I want to write a game server which has one thread for all clients to handle messages, and use something like epoll to accept networking messages. All i/o and database access will be processed in thread pool and they are asynchronous and non-blocking. My questions are :

1. How should I handle other events/messages like physics, game logic etc.? Can I implement methods to handle these messages as blocking interface in the main thread?

2. Is there simple open source popular server(like cocox*d/unity as client) which implemented this way that I can reference.

I want to write a game server with one thread for clients message handling and use something like epoll to accept network messages. All I/O and database access will be processed in a thread pool and they are asynchronous and non-blocking.

Given such a scheme, how should I handle other events/messages (physics, game logic, etc)? Can I implement methods to handle these messages as a blocking interface in the main thread?

What simple, popular servers exist (using Cocos*d/Unity as client) that I could look at for an example of this?

I want to write a game server which has one thread for all clients to handle messages, and use something like epoll to accept networking messages. All i/o and database access will be processed in thread pool and they are asynchronous and non-blocking. My questions are :

1. How should I handle other events/messages like gui, game logic etc.? Can I implement methods to handle these messages as blocking interface in the main thread?

2. Is there simple open source popular server(like cocox*d/unity as client) which implemented this way that I can reference.

I want to write a game server which has one thread for all clients to handle messages, and use something like epoll to accept networking messages. All i/o and database access will be processed in thread pool and they are asynchronous and non-blocking. My questions are :

1. How should I handle other events/messages like physics, game logic etc.? Can I implement methods to handle these messages as blocking interface in the main thread?

2. Is there simple open source popular server(like cocox*d/unity as client) which implemented this way that I can reference.

I want to write a game server which has one thread for all clients to handle messages, and use something like epoll to accept networking messages. All i/o and database access will be processed in thread pool and they are asynchronous and non-blocking. My questions are :

1. How should I handle other events/messages like gui, game logic etc.? Can I implement methods to handle these messages as blocking interface in the main thread?

2. Is there simple open source server if I adopt cocox*d as client side?

I want to write a game server which has one thread for all clients to handle messages, and use something like epoll to accept networking messages. All i/o and database access will be processed in thread pool and they are asynchronous and non-blocking. My questions are :

1. How should I handle other events/messages like gui, game logic etc.? Can I implement methods to handle these messages as blocking interface in the main thread?

2. Is there simple open source popular server(like cocox*d/unity as client) which implemented this way that I can reference.