[JDEV] Q: message tracking

Wed Jun 13 11:29:04 CDT 2001

Peter Saint-Andre wrote:

> I've usually seen the 'id' attribute used to correlate an iq set with an
> iq result and such, not for messages. The server seems to be consistent
> about returning the 'id' attribute for iq packets, but clients don't seem
> to be consistent about returning the 'id' attribute for message packets.
>
> But I'm just speaking from my experience playing around with sending raw
> XML, I'm not sure exactly how the system is designed to handle 'id'
> attributes. :)
>
> Peter
>

that's why I'd assumed that message id's associated w/ the response to a message might
reflect the original message id - either explicitly or some logical derivation .

from the protocol doc______________________

1.3.2.2. The ’id’ attribute Applies a unique identifier to the message. The ’id’
attribute is generated by the Jabber client or client library (e.g., WinJab or
JabberCOM), and is used by the client to identify the message for tracking purposes
(e.g., to correlate messages sent to a groupchat room with messages received from the
room, or to connect a sent message with any errors it might generate). The ’id’
attribute is optional and is not used elsewhere in the system.
Example:
<message to="romeo at montague.com/orchard" id="JCOM_85">
<body>Wherefore art thou Romeo?</body>
</message>
_______________________________________

is there a recommended way to establish the sequence and lineage of exchanged messages
for non-chat message types ??

thanks for the response