[Wocky] Adium auto-reconnect issue

[Greg Hudson]

If you log into jabber.mit.edu from two different machines with the
same resource, your first login will be terminated.  This is intended
behavior.

When Adium sees a terminated connection, it automatically reconnects
after two seconds.  This creates a ping-pong effect when two Adium
clients try to connect with the same resource.  I have my suspicions
that ping-ponging Adium clients may be responsible for the occasional
loading issues we've been seeing on jabber.mit.edu, especially if our
Kerberos password-authentication code is a bit inefficient (for
instance, I think it synchronously waits for a response from the
Kerberos server, blocking all other activity in the c2s process which
handles all connections).

When Gaim sees a terminated connection, it displays a dialog and
offers to reconnect, so there is no ping-ponging issue.

Things we can do:

  * Report this issue upstream to Adium.  Bob, I'm dropping this on
    your plate.

  * Make our password authentication code more efficient.  Not sure if
    this is technically feasible.

  * When we receive a second connection on the same resource, block
    the new connection instead of the old one.

  * When we receive a second connection on the same resource, force
    the use of a different resource.

I will work on the last option.