------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=126145
sven.burmeister gmx net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sven.burmeister gmx net
------- Additional Comments From sven.burmeister gmx net 2006-09-20 14:14
-------
I see this too with wildfire and PyICQt/MSNt. I had added the transports in
another program. When running kopete after that it does not recognise the
transports, i.e. no extra account icon in the status-bar. They do work though.
After a transport throws an error, e.g.:
"Failed to connect to MSN servers: [Failure instance: Traceback (failure with
no frames): exceptions.Exception: Timeout
]"
the transport is recognised.
My first guess is that kopete just forgets to ask the contact (transport) what
category it belongs to. I am not sure if kopete should ask all contacts or wait
for some trigger, e.g. a JID without an @ or if it gets asked for disco, to ask
back:
XML IN: <iq from="icq.jabber.rwth-aachen.de"
<query xmlns="http://jabber.org/protocol/disco#info"/>
</iq>
If it would ask the relevant contact:
XML OUT: <iq type='get'
from='ssssssssss jabber ddddddd aa'
to='icq.jabber.ssssssssss.aa'
id='info1'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
It would get an answer which clearly states that the contact is a gateway.
XML IN: <iq from="icq.jabber.sssssssssss.aa" type="result" to="sssssssssssss
jabber sssssssssss aa/Kopete" id="info1" >
<query xmlns="http://jabber.org/protocol/disco#info";>
<identity category="gateway" type="icq" name="ICQ Transport" />
<feature var="http://jabber.org/protocol/disco"; />
<feature var="http://jabber.org/protocol/commands"; />
<feature var="jabber:iq:register" />
<feature var="jabber:iq:last" />
<feature var="jabber:iq:gateway" />
<feature var="jabber:iq:version" />
<feature var="jabber:iq:time" />
<feature var="vcard-temp" />
</query>
</iq>
Another possible trigger for asking could be a message from a node:
XML IN: <presence from="ssssssssssss%sss.aa
<c xmlns="http://jabber.org/protocol/caps";
node="http://msn-transport.jabberstudio.org/protocol/caps"; ver="0.11.2-dev" />
</presence>
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
