nu.kanga.list.mud-dev

27208: Re: [MUD-Dev] New to MUD Dev, need friendly advice!

On Apr 27, Zach Collins (Siege) wrote:

> There are three options.  Twisted (http://www.twistedmatrix.com/)
> uses a single process.  Many web servers fork new processes to
> handle incoming requests.

AFAIK, virtually no modern web servers fork to handle each new
incoming request, though some will pre-fork a pool of processes into
which requests are thrown for handling.  fork() is still just too
expensive in the general case, and HTTP request-connections are too
short-lived.

That's likely different in the MU* space, though, where connections
will tend to live many minutes rather than a few dozen microseconds.
In that case, doing whatever's easiest to reason about (fork for
each client, process pool, thread pool, thread creation; "easiest to
reason" is very much a personal style issue) is likely the winning
approach, because the cost of the fork/thread_create will be below
the noise floor.

Mike

_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev