Whole 6. Entity Use Cases
must be checked and implemented missing parts
Especially needed:
extended info
disco#items
yeah, please finish it. i'm currently trying to get the number of occupants in a room and do send the following:
<iq to='world@muc.example.com' type='get' xmlns='jabber:client'><query xmlns='http://jabber.org/protocol/disco#items'/></iq>
the response is
<iq from='world@muc.example.com' to='tom@example.com/console_666' type='error' xmlns='jabber:client'><query xmlns='http://jabber.org/protocol/disco#items'/><error code='501' type='cancel'><feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xml:lang='en' xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'>To be implemented!</text></error></iq>
that feels wrong.
Updated issue with changes needed/related for "no presence" mode.
Whole 6. Entity Use Cases
must be checked and implemented missing parts
Especially needed:
extended info
disco#items