[JDEV] A Protocol Dev. Carification

[Rachel Blackman]

> Of course, it is not possible to programmatically account for the SHOULD
> behavior on results and errors; the whole point of the 'id' is to enable
> endpoints to match asynchronous requests with their responses. Perhaps
> something to bring up to the XMPP working group?

Hrm...you're right.  But that seems like a pretty significant oversight;
either ID is useless (if you can't expect it to be returned) or it's
declared wrong.  If id /isn't/ required, then Exodus and a number of other
things (including my own Jabber implementation for Trillian), which rely on
ids for a few things are in violation of the specification.

Urgh. :/

-- 
Rachel Blackman <rcb at ceruleanstudios.com>
Trillian Messenger - http://www.trillian.cc/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20030430/c39a2288/attachment-0002.pgp>