What is better?

[[GMs]]

Vote in the poll.

[|BasicCoder|]

Originally Posted by [GMs]

Vote in the poll.

Whats the point in this? Lol

[airborne.]

I think he means if it's better to have a Login server and Game server separate or just 1. Like Coemu has login and game server, and 5165 source has 1 exe.

[SimplyPerfection]

You don't have two servers, you have one login which will handle all the auth, and a gameserver which will handle the game, easy as that.

Ofcourse it's better to seperate login and gameserver as the gameserver shouldn't be affected from the authentication, just from receiving what the loginserver sends onto the game.


In short terms;
Have seperated login and gameserver.

[Korvacs]

Definately have a Login and a Game server seperately.

[airborne.]

Originally Posted by Korvacs

Definately have a Login and a Game server seperately.

Unless the Login server overloads constantly and crashes.

[Korvacs]

Originally Posted by airborne.

Unless the Login server overloads constantly and crashes.

If thats the case, write a new login server which doesnt overload all the time.

The game server should concentrate 100% on dealing with clients on the server, not authenticating. Why waste threads on authenticating when a seperate server should be doing that by design?

[Zion~]

It's also easier to manage. If the login server crashes it doesn't affect the game server, you could also program the game server to start the login server if it has crashed by checking if its process is running.

Other advantages would be you could have several game servers linking to 1 login server, and my favorite advantage is the ability to run the login server on a different machine from the game server without any error. (When starting big servers, its most wise to run your login server on a separate vps from your game server) Sorry I can't think of any disadvantages.

[LetterX]

Originally Posted by airborne.

Unless the Login server overloads constantly and crashes.

If the auth server crashes, then that would force you to restart the game server too. If that code were unstable, connecting it to the game portion wouldn't make it any more stable.

I don't think you can really screw up the Auth server considering it's so simple. Receive, Authenticate, Send (or disconnect).

edit: I voted for separate servers.

[~Falcon]

Originally Posted by Zion~

It's also easier to manage. If the login server crashes it doesn't affect the game server, you could also program the game server to start the login server if it has crashed by checking if its process is running.

Other advantages would be you could have several game servers linking to 1 login server, and my favorite advantage is the ability to run the login server on a different machine from the game server without any error. (When starting big servers, its most wise to run your login server on a separate vps from your game server) Sorry I can't think of any disadvantages.

^

The ONLY disadvantage that comes to mind, is passing data from authentication to the game server, obviously not such a hard task. But you need to make sure its not exploitable, or you'll be having a field day like myself and another individual did on acidco

[hunterman01]

Originally Posted by ~Falcon

^

The ONLY disadvantage that comes to mind, is passing data from authentication to the game server, obviously not such a hard task. But you need to make sure its not exploitable, or you'll be having a field day like myself and another individual did on acidco

Gotta be saint

[~Falcon]

Originally Posted by hunterman01

Gotta be saint

Incorrect, care to try again?

[hunterman01]

Lol not really : /

[_tao4229_]

it's not me

[Korvacs]

Originally Posted by ~Falcon

^

The ONLY disadvantage that comes to mind, is passing data from authentication to the game server, obviously not such a hard task. But you need to make sure its not exploitable, or you'll be having a field day like myself and another individual did on acidco

I dont send any data between my auth and game servers anymore =o!