Game Development Reference
In-Depth Information
In the early authentication scheme, the authentication is verified before the
connection to the session server is established. If the authentication passes, the login
server will inform the appropriate session server to expect a login from the client.
The session server will receive the username, and for additional security, a session
key is also passed. This session key is also sent to the client, so when the client
connects to the session server, the client sends the username and the session key for
the session server to validate the connection. Notice that this scheme further splits
the responsibility to another process, the login server.
In lazy authentication , the session server is responsible for initiating the
authentication and either accept or deny the request. The lazy authentication
is much simpler than the early authentication mechanism.
Dealing with multiple logins
The one common issue that must be dealt with in a public deployment is the issue of
multiple logins. There are two options that could be implemented when a duplicate
login is detected:
1. Disallow the second login.
2. Disconnect the first login.
 
Search WWH ::




Custom Search