> Have you found that people actually want this functionality?? I had threads > properly implemented in Winjab a _LONG_ time ago, and every single user > complained about it. "Why does a new window open up???". This was mostly > because other clients were not echo'ing my thread tag back. Thus, you end > up having a "bucket" chat window which receives all messages which have a > blank thread. Most of this could be avoided if the <thread> tag was > mandatory for message type="chat" packets. I've long since gotten away from > the idea of trying to implement threads "properly" because of these reasons > (other clients).... Mostly, I just echo the last thread, and generate one > when a new conversation starts.
As a latecomer to the world of Jabber clients, my first instinct was that since it was not a requirement, and most clients didn't support it, that I would not bother supporting it either... Also, the concept of thread start/end is up to the client. What if I still have my window open, but my friend has for some reason closed/re-opened his? I don't want to have a new chat window on my end just because of my friend's behavior. > On a related note, many clients don't handle chatting w/ multiple resources > very well either. Again, this is an "edge case" IMO, but once that can be > important in certain vertical market applications. This is huge, I think, and deserves a catagory on the jabber.org clients listing page. -Justin _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
