[JDEV] Messaging with Resources, desired behavior

[Dave Smith]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Monday, May 26, 2003, at 19:38 America/Denver, Justin Karneges wrote:

>> Well, Nitro and Exodus both "lock in" to a resource once a reply is
>> sent. So they send the initial message to user at host, then
>> user at host/resource once a reply comes back. The trick here is that 
>> once
>> the "locked in" resource goes offline, you switch back to sending
>> messages to user at host. Repeat when a reply comes back from another
>> resource.
>
> Generally, a client limits one chat window per JID.  How do you handle 
> a
> 'switch back' when there are two active resources?

I don't know about Exodus, but Nitro ensures that only one windows is 
ever registered for user at host events. So if you get two chats locked 
in, then both get unlocked, the last one to unlock gets to receive 
future messages from user at host.

>   8) EMM386.SYS error

OSX doesn't need an EMM386.SYS driver. ;)

Diz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)

iD8DBQE+0seQYNE3chVHHsMRAi/jAJ4hDsKPdJ40EENz9cCPrwnHvsFO4wCeJlK8
FvHN8apFmjP5QaRuaFQV6l8=
=CZlE
-----END PGP SIGNATURE-----