[JDEV] Messaging with Resources, desired behavior

[Justin Karneges]

> 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?

  1) Open chat to user at host
  2) Receive message from user at host/res1
  3) Chat window magically changes its JID to user at host/res1
  4) Receive message from user at host/res2, causing a second chat window to 
appear
  5) user at host/res1 goes unavailable
  6) chat window reverts JID to user at host.
  7) user at host/res2 goes unavailable
  8) EMM386.SYS error

-Justin