[JDEV] thread tracking with aim-transport

[Eric Bowersox]

> If I fire off an IM to a AIM client, along with a <thread> tag, when I
> get a response back it doesn't have the appropriate thread identifier
> attached, which makes it tough to juggle multiple conversations.  
> 
> Is this a known thing?

Yes, and it's a known thing with icq-transport as well.

The problem here is that an AIM or ICQ message has no thread identifier, so
how do you figure out which one to use?  If you use the last thread
identifier that a Jabber user sent, does that mean you have to track "last
known thread" for every combination of transport user and person on their
AIM buddy list or ICQ contact list?  What's that going to do to your memory
requirements?  And what if the AIM or ICQ user sends the Jabber user a
message *first*; what thread identifier do you use then?  It's a fairly
messy problem, so the AIM and ICQ transports ignore it for the time being;
this may not be true forever though.  (No comment on how long it may be...)

					Eric