[JDEV] jabberd patch

Tijl Houtbeckers thoutbeckers at splendo.com
Tue Feb 25 08:52:43 CST 2003

"Richard Dobson" <richard at dobson-i.net> wrote on 25-2-2003 15:30:10:
>> 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.
>That issue can be solved pretty easily, the client that is getting 
>logged off because another one is connecting just needs to be notified 
>of the reason of disconnection and if it is because another client has 
>logged on you pop up a box or something and dont try to auto-connect 
>again (just like the MSN protocol does). There can be issues with 
>logging off the old connection and letting the new connection in as 
>jabber does now, but I think it is much better than the reverse as 
>more serious problems happen doing it the other way. If the only 
>problems are things such as this that can be pretty easily solved then 
>we should leave it as is, this is all about a weighing of benefits 
>against problems and I think the current method jabber uses has 
>definate benefits that outweigh the problems pointed out so far. 

Until the problem is solved on the protocol level and enough clients 
support it this patch could still be usefull for some. Besides that it 
should be possible to prefer this method is some specific cases, so if 
we fix this we should also include the *possibility* for the server to 
deny a client during login because another session with the same 
resource excists. (This should be no more than adding an error code I 

Tijl Houtbeckers
Software Engineer @ Splendo
The Netherlands

More information about the JDev mailing list