[jdev] Thread IDs - The Reality?

[Trejkaz]

On Sat, 13 Aug 2005 04:49, Tijl Houtbeckers wrote:
> When a client sends back messages of type="chat" without a thread ID, then
> you know there's only "one thread". (thus clients that do support multiple
> threads know not to open more than one thread to that clients, because
> messages would get mixed up between them). What else would you want a
> thread ID for? To maintain some sort of session? The behaviour for that is
> *very* undefined, so I would advise not to rely on it.

I'm dealing with this exact problem in bot code.  My bot supports threads, and 
gives the user one session per thread if the user initiated the conversation.  
If the bot initiates the conversation, it sends a thread ID but if the user 
responds without one, the bot clears its thread ID and gives the user just 
one session.

At the time, I think I even remembered reading that responding with a thread 
ID is an indication that you support multiple threads.  So claiming you do 
and then not doing it would definitely be bad behaviour.

TX

-- 
             Email: Trejkaz Xaoza <trejkaz at trypticon.org>
          Web site: http://trypticon.org/
         Jabber ID: trejkaz at jabber.zim.net.au
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20050813/d3233101/attachment-0002.pgp>