[standards-jig] UPDATED: Commands (JEP-0050)

Casey Crabb crabbkw at nafai.dyndns.org
Tue Jan 21 19:35:08 UTC 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A few comments:
When getting information on a command using disco the jep has the
following protocol:

<iq type='get'
~    from='requester at domain'
~    to='responder at domain'>
~  <query xmlns='http://jabber.org/protocol/disco#info'
~      node='config'/>
</iq>

The part I have problems with is node='config'. Since this request isn't
namespaced to commands its not obvious that we're trying to get
information about a command and not information about client
configuration or something else. My recommendation is that all command
nodes are named as a sub-namespace of the command namespace.
Example:

config would become http://jabber.org/protocol/commands#config

So the full new request would look like:

<iq type='get'
~    from='requester at domain'
~    to='responder at domain'>
~  <query xmlns='http://jabber.org/protocol/disco#info'
~      node='http://jabber.org/protocol/commands#config'/>
</iq>

This will prevent help collision and confusion with other nodes in
disco. The response with the list of commands will have to be changed as
well to match.


Secondly in Example 6, "the responder MUST respond with a 403
'Forbidden' error."  -while I agree that it should be this way for
compliance, implementations should not rely on getting any response from
the other side.

questions, comments?

- --
Casey

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQE+LaDsUidG/HUEju8RAqjhAKCpDHf8ch89C87Ef8f8NoYf6DV9hwCVGhgD
mjoBCmou0dllQSuJZcsmJQ==
=Ai6W
-----END PGP SIGNATURE-----




More information about the Standards mailing list