[Standards-JIG] JEP 50, Ad-Hoc Commands

Jacek Konieczny jajcus at bnet.pl
Fri Feb 13 08:45:34 UTC 2004

On Thu, Feb 12, 2004 at 10:26:20PM -0800, Chris Mullins wrote:
> It seems very incorrect the way node names from ad-hoc commands pollute the
> global node namespace for a JID.

I don't think so.

> Example 5 in JEP 50 shows the XML:
>   <query xmlns='http://jabber.org/protocol/disco#info'
>          node='config'/>
> The entities is supposed to then scan it's node list, and return the node that
> matches on "config". This seems very restrictive, as it REQUIRES there only be
> a single node called "config" present for the "to" JID.

But if it is called "config" or something else is defined by entity
addressed by JID and discovered using disco#items query to
"http://jabber.org/protocol/commands" node. It is the entity responsible
to make it so it doesn't conflict with any other nodes in the entity.


More information about the Standards mailing list