[Wocky] 2 instances of Jabber, with Adium

[Greg Hudson]

On Tue, 2007-02-27 at 12:08 -0500, Ken Raeburn wrote:
> There's been some discussion in the past about which client will get  
> messages when you have multiple connections.  The priority value of  
> the connection can determine this, and Adium lets you select priority  
> values to use when you're "available" versus "away", though I don't  
> know what the default value is (for Adium, or if Jabber has a  
> standard default priority value... anyone?).  So if Adium marks you  
> as "away" if you're idle for a while, like if you've gone to work  
> while leaving yourself logged in at home, and you've set the  
> "available" and "away" priorities properly, you shouldn't have to  
> worry about missing any messages while you're using one of your  
> computers; if you're "away" from both, though, messages could wind up  
> not going to the computer you next sit down at.

The default priority for just about any Jabber client is 0.  So the
normal case is that all clients have the same priority.  In this case,
the server will generally send messages to the client which logged in
most recently.  (I did prepare a patch to make messages get sent to all
highest-priority clients in this case, but it was never deployed.  I may
try again with that when we switch to Wildfire.)

Regardless of how the server handles that situation, if you were in the
middle of a conversation with someone at home, and your conversation
partner still has a window open from that conversation, messages typed
into that window will be sent to your "full jid" (with resource),
forcing them to go to your home client.  This practice keeps
conversations in one place, but is decidedly inconvenient when it causes
you to miss messages.  Moral: close Jabber conversation windows after
long gaps in the conversation, just in case the person you're talking to
has switched clients.