hi
XEP-0030 (http://www.xmpp.org/extensions/xep-0030.html#items-basic) specifies that:
“The target entity then MUST either return its list of publicly-available items, or return an error.”
All gateway protocols return just an empty IQ result.
src/plugins/gateway/src/java/org/jivesoftware/wildfire/gateway/BaseTransport.jav a, method handleDiscoItems
This can easily be fixed by returning the same features as that returned by handleDiscoInfo.
The result of the empty IQ result is that some clients, such as bombus (http://bombus.jrudevels.org/), cannot register with the gateway transports.
roelof wrote:
hi
XEP-0030 (XEP-0030: Service Discovery) specifies that:
“The target entity then MUST either return its list of publicly-available items, or return an error.”
Right… but I am sending a list of publically available items, it just so happens that that list is empty. See Example 13.
All gateway protocols return just an empty IQ result.
src/plugins/gateway/src/java/org/jivesoftware/wildfire/gateway/BaseTransport.jav a, method handleDiscoItems
Right, since the transports have no items, to handle, they return an empty list as they shold.
This can easily be fixed by returning the same features as that returned by handleDiscoInfo.
Why would I do that? Those are features not items.
The result of the empty IQ result is that some clients, such as bombus (http://bombus.jrudevels.org/), cannot register with the gateway transports.
It ought to be able to follow the procedure as outlined in XEP-0100, gateway interaction, and request the disco -info- (not items) and see jabber:iq:register as a feature supported, and hence know that the transport supports registration. There is nothing in XEP-0100 that indicates that I should be returning any sort of items response that relates to jabber:iq:register.