Cluster Support: Difference between revisions
Content deleted Content added
imported>Hendrik Brummermann initial stub |
imported>Hendrik Brummermann Messages and structure of tasks |
||
Line 10:
As the clients connect directly to the nodes, there needs to be some mechanism to tell a client to which node to connect.
; MessageS2CLoginACK : will be extended to contain a session id, it needs to be encrypted similar to the password transmission
; MessageS2CForward : The current node tells the client to disconnect and reconnect to the node specified in the message
; MessageC2SReconnect : A quick way to login. Assuming that all nodes use the same key, the key exchange can be shortened. The selection of character step can be skipped, too, because the sessionid is bound to a character.
=== Communication Node - Node ===
== Tasks ==
=== Authentication ===
=== Cross node zone change ===
=== Cross node teleports ===
* Target allowed to teleport into?
=== Online/Offline notifications ===
=== Cross node actions ===
* /tellall
* /msg
* /who
* /where
=== Cross node admin actions ===
* /inspect
* /script DeepInspect.class
== See also ==
| |||