Cluster Support: Difference between revisions

* [http://www.jgroups.org/ jgroups] looks good with a [http://www.jgroups.org/api.html nice API], but the .jar file is huge (3 MB).

When the client connects to a different cluster node, it has to authenticate it self. In order to support the inital web based login with a one time secret, the username/password cannot be used. There are two alternatives:

* The login secret can be part of MessageS2CForward, This approach has the advantage that code for the login is already there for the web based login.

* Use a sessionid that is generated on login and valid until the player logs off (or 5 minutes after he is last seen). This sessionid has to be maintained the server side and a new login message is required. On the positive side this sessionid can be used for reconnecting after the connection was lost.

[[Image:Cross node zone change.png|thumb|Cross node zone change]]

Cross node zone change require the client to connect to another server:

Problems:

* Client may disappear during zone change

* Target zone server may be unavailable

* See [[Cluster_Support#Online.2FOffline_notifications online/offline]] section.

{{br}}