[JDEV] .. double-connect ..

[Edward J Becker]

Yes, after some thought, I think the best way to handle it is that clients
should determine their resource name using some sort of cpu-id based
identifier in addition to their client resource name.  This way, you can
have multple clients logged in from multiple machines.  It should be an
install-based configuration deal.

Edward




-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
Thomas Charron
Sent: Tuesday, December 12, 2000 8:16 AM
To: jdev at jabber.org
Subject: Re: [JDEV] .. double-connect ..


    That's basically becouse the server replaces the old session with the
new one, which is what your looking for..

    Unfortionatly, the *CLIENT* is the issue here.  It's going into a
reconnect loop, causing the issue.  Turn off the reconnect option in
whatever client you are using..

From: Jens Langner <Jens.Langner at newtron.net>
Subject: RE: [JDEV] .. double-connect ..
> But what happens if the same user tries to connect to the same server with
> the same resource ?? I mean in my case the same user connects with two
> computers with the same resource to the jabber server and the two JabberIM
> clients are playing ping-pong with the online status of the user.



_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev