[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    Re: [JDEV] JEP-51 Server Transfer
From:       Richard Dobson <richard () dobson-i ! net>
Date:       2002-11-28 3:47:12
[Download RAW message or body]

Well thats really got nothing to do with the protocol itself, its got 
to do with the server implementation and how its farming in that 
implementation works, if the server is done properly it wouldnt matter 
which server in the farm you are connected to you would always get the 
messages that are addressed to you, btw the reference jabber server is 
not currently designed for this kind of farming (complete servers 
acting together as one).

On Wednesday, November 27, 2002, at 02:23  pm, Heiner Wolf wrote:

> Hi,
>
> I am building a load balancing system for the users of a jabber based 
> virtual presence project http://jabber.bluehands.de/
>
> I write a connection redirector and discovered:
> Szenario: client connects and logs in to "jabber.org". Then the client 
> gets an iq-"Server Transfer", disconnects, and connects to another 
> server e.g. "server2.jabber.org". How do other clients and servers 
> (s2s) know that the client is connected to "server2.jabber.org". They 
> will still know the user as "user@jabber.org" and send messages 
> through s2s to "jabber.org", not to "server2.jabber.org" where the 
> user is connected.
>
> Questions to the public: does JEP-51 Server Transfer work, if messages 
> (IMs) arrive from other users in other domains? What did I miss?
>
> Regards
> --
> Dr. Klaus H. Wolf
> bluehands GmbH & Co.mmunication KG
> http://www.bluehands.de/people/hw
> +49 (0721) 16108 75
> _______________________________________________
> jdev mailing list
> jdev@jabber.org
> http://mailman.jabber.org/listinfo/jdev


_______________________________________________
jdev mailing list
jdev@jabber.org
http://mailman.jabber.org/listinfo/jdev
[prev in list] [next in list] [prev in thread] [next in thread]