On Thu, 2003-04-03 at 08:12, Bert Radke wrote: > On Wed, 02 Apr 2003 15:29:42 -0600 > Justin Georgeson <[EMAIL PROTECTED]> wrote: > > > Jabber is an asynchronous protocol, hence the ID attribute. > Yes, but I thought the ID is for matching a response, not for ordering > the messages.
Not quite. In an IQ conversation, this is correct. However. in messages, the id really only allows one to track the messages, and to confirm the relationship between the message as sent from one end, and recieved on the other. Copying the 'id' tag for message replies is fundamentally a bad decision. If a reply-to-the-reply is produced under the same circumstances, then you'd have one client sending out two messages with the same ID in the same session, effectively eliminating any usefullness of that attribute. If you plan to track all messages that "belong" to a particular conversation, you probabbly want to be using the "thread" child tag. As for a way to track what message a given message is in response to... I'm not aware of a current solution for that. -- Jeremy Nickurak -= Email/Jabber: [EMAIL PROTECTED] =-
signature.asc
Description: This is a digitally signed message part
