> A "compliant" client IMO, should at least do the following: > > 1) Client SHOULD Always generate a new <thread/> when a new conversation is > started. In most clients, this is equivilant to dbl-clicking on the contacts > glyph in the roster. A new window is opened, so I get a new thread. > > 2) Clients MUST always echo back the <thread/> tag when replying to existing > chat messages. > > If all clients at least did rule #2, I would be happy to put proper > threading back into my clients :) >
This gets tricky when you're dealing with a command-line client. How do you know what is replying and what is starting a new conversation? This is the way I solved it. If I've never received a message from them, or I haven't received a message in the last n (I think I set n to 5 minutes) time units, I start a new thread. Otherwise I echo back the thread last sent to me. Do you think this is an appropriate solution? -- Casey _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
