Multithreaded Server / Client structure.

Krylloan · 2004-06-19T11:31:47

Is this a decent multi-threading server-client setup? (Very pseudo-code. "lis", "acc" and "cli" are socket descriptors. "acc" can be multiple descriptors.) "run" is shorthand for create new thread starting at this function. ----------SERVER----------- SERVER_THREAD: (Main Server Program Thread) ------------- lis = socket() bind(lis) run LISTEN_THREAD --continue with game-- close(all acc''s) close(lis) LISTEN_THREAD: (A Secondary Server Thread) ------------- listen(lis) loop(if not closing) { acc = accept() run ACCEPT_THREAD } ACCEPT_THREAD: (Multiple Server Threads) ------------- recv(acc) ----------CLIENT----------- CLIENT_THREAD: (Main Client Thread) ------------- cli = socket() connect(cli) run CONNECT_THREAD --continue with game-- close(cli) CONNECT_THREAD: (A Secondary Client Thread) -------------- recv(cli) Is this a good network layout for a game? Is close() the correct way to abort the recv() and accept() calls? Thanks for all comments.

Networking and Multiplayer Programming

Started by Krylloan June 11, 2004 06:37 AM

9 comments, last by hack 19 years, 10 months ago

hack

122

June 19, 2004 11:31 AM

I have made a server by select() under linux.
It can handle 500 connections, if single operation doesn't cost too much.

I am thinking of making a multithread server by dividing map into zones, one zone one thread, this may reduce the syncronizing problem.

Multithreaded Server / Client structure.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Multithreaded Server / Client structure.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines