[JDEV] jabberd patch

[Richard Dobson]

> >> Then again, not using this patch has it's own problems when two clients
> >> with auto-reconnect start to "fight" over the same connection. So this
> >> patch is definatly usefull for those who want to avoid this type of
> >> behaviour.
> > I am not sure which I prefer, but I think there should be only one,
defined
> > behaviour for connecting with the same resource as an already connected
> > client.
>
> It may make sense to kick the old client (as it is done with the
> out-of-the-box-jabberd currently) but I'd strongly suggest to include this
> into karma somehow. The ping-pong scenario described above leads to
> problems with transports and rather high server load here.

As noted in a message I just sent (not arrived on the list yet), you can add
manditory client logic so clients kicked off because of another client
logging in are not allowed to automatically re-login without user
intervention, and to preferably display a popup telling the user the reason
they were logged off (i.e. another client has logged on.....).