On 10/3/2011 8:05 PM, Mike Wacker wrote:
I've checked a new provisional version of XEP-0045 into git...
Latest diff:
http://xmpp.org/extensions/diff/api/xep/0045/diff/1.25rc6/vs/1.25rc7
Diff from 1.24:
http://xmpp.org/extensions/diff/api/xep/0045/diff/1.24/vs/1.25rc7
Rendered version:
http://xmpp.org/extensions/tmp/xep-0045-1.25.html
Continued feedback would be appreciated.
/psa
It may help to include the full end-to-end flow for discovering
component support for MUC. Unlike other features, MUC often must live on
a separate domainpart (chat.shakespeare.lit) than the one an entity
negotiates a stream with (shakespeare.lit); otherwise it would be
impossible to tell if [email protected]/pda is a full jid or a room
jid.
In 6.1, the [email protected]/pda send a disco#info request to
chat.shakespeare.lit, but it never says how hag66 determined that
chat.shakespeare.lit exists in the first place.
Doing some digging around in XEP-0030, it appears that the answer would
be this:
1. [email protected]/pda issues a disco#items request to
shakespeare.lit. One of the items returned is chat.shakespeare.lit.
2. [email protected] issues a disco#info request to each item
returned in (1). The disco request to chat.shakespeare.lit returns the
muc feature.
It might be helpful to list out those steps as well. In addition, I
would assume that shakespeare.lit MUST NOT return the muc feature in a
disco#info request, since it itself does not support the muc feature
even though it has an item which supports the muc feature.
Mike
