[JDEV] A Protocol Dev. Carification

[David Waite]

nope, from 
http://www.jabber.org/ietf/draft-ietf-xmpp-core-11.html#stanzas-attributes-id 
:

The optional 'id' attribute MAY be used to track stanzas sent and 
received. The 'id' attribute is generated by the sender. An 'id' 
attribute included in an IQ request of type "get" or "set" SHOULD be 
returned to the sender in any IQ response of type "result" or "error" 
generated by the recipient of the request. A recipient of a message or 
presence stanza MAY return that 'id' in any replies, but is NOT REQUIRED 
to do so.

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?

-David Waite

Rachel Blackman wrote:

>>    I wish to thank you for the solution.  And I would like to thank
>>everyone for their help. I discovered that the 2 clients (Gaim .62 and
>>Exidous .8) I started with require the ID tage returned.  This is a far
>>cry from what I read.  First off, this issn't the case when I create a
>>user using Gaim.  I have yet to figure out how to get Exidous to allow
>>for user creation.  Second, The standered says "May Return ID tag," both
>>gaim and exidous require it.
>>    
>>
>
>My understanding is that the origin of a stanza MAY set an id in the
>stanza.  If that is the case, whatever responds to the stanza MUST include
>the id in the reply.  In other words, if the client includes an id tag, the
>server must return the id tag in the reply.  Similarly, if I as a client
>respond to, say, a jabber:iq:version request, if the other client included
>an id in their request, I must include it in my reply. :)
>
>  
>