ID:92732
 
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
This goes along with request 1188

In my prior suggestion, I mentioned a method for easing the transition between worlds in a cluster-based game, where the world is split between multiple servers.

I think if this system exists, the developer should be able to "lump" their live game data, so that in a four server setup, three being slaves, and one being a master.

The master server will be the only game of the four servers listed live, and all players logged into each slave world will be listed under the master world. When a player attempts to join a slave world, he is redirected instantaneously to the master world without directly connecting to the slave. That is, unless the player is linked directly to that slave world from within another server in the cluster.

Live Hub entries should be allowed multiple clusters, and clusters should have some method of authenticating one another upon World creation. If the authentication fails (via a new world function), the world is hosted as an independent (or master) server of its own cluster.
Thinking about it, preventing login to a slave server wouldn't be hard with the current system, you'd just have to link() from one server to the master, and then send a topic to a slave when linking to tell it to expect that player to show up. =/