[jdev] XEP-0115: Entity Capabilities
jdev at monitzer.com
Fri Jun 22 22:14:12 CDT 2007
Tonight I implemented XEP-0115 into libpurple (the receiving end, not
the sending one). When testing it, I discovered that both Gajim and
the py-transports (pyaim-t and pyicq-t) don't implement this properly
at all (my only two test candidates I had available in addition to my
own implementation). Do I miss something here?
Both announce their capabilities by that extension to the presence
stanza, Gajim even announces two ext values, ftrans and xhtml.
However, Gajim does not respond to disco#info queries to those nodes,
and replies with a generic disco#info reply instead. The py
transports use the same stanza for both themselves and their clients,
which do not have the same features, so my client has a misconception
about the capabilities, depending on which one it asks first.
Is this XEP not really expected to be implemented by anybody? If so,
why do all clients announce <c xmlns='http://jabber.org/protocol/
caps'/> in their presence stanzas?
Maybe I should just file bug reports with those projects and hope
that they will get fixed some time in the future...
More information about the JDev