[JDEV] ICQ over AIM bugs

[Julian Fitzell]

Well, that's certainly how it *should* work but the old ICQ transport 
never worked that way for me... it always sent messages to the first 
resource that connected to it... was very frustrating when logging on 
from school and people sending me icq messages would have them routed to 
my client at home.

Julian

Michal Leinweber wrote:

>>>AFAIK only the client that connects first is able to use AIM/ICQ.
>>>Theoretically it should be possible to modify this behaviour but it
>>>requires some work.
>>>
>>>
>>The problem is - one jabber account does not map to one AIM account or
>>ICQ account; one Jabber session maps to one of these accounts. So, if
>>your '/Work' resource sends a message to an ICQ user, how could a
>>transport possibly know to route messages back to it instead of a
>>different resource?
>>
> 
> Ohhh, stop, and think a bit!
> As in old ICQ Transport!, messages are routed to the highest priority
> resource!
> This is the same as main jabber philosophy. When somebody sends message to
> user at jabber.org, then message is routed to the user's resource with highest
> priority! And I think this is the best method.
> 
>     McLEI
> 
> PS: In my client I have implemented forwarding of waiting messages from
> clients when new higher priority resource connects.
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>