3 ms·
Why does the blog posting only mention fork and prefork as options? A very common way to design servers is to do multiplexing IO. The one-connection-per-threa
by bborud 13y ago
Why does the blog posting only mention fork and prefork as options? A very common way to design servers is to do multiplexing IO. The one-connection-per-thread/process isn't the only way.
That being said, this option can simplify things -- removing the necessity of having some moving part to distribute connections across completely independent processes.
- joosters 13y agoThey aren't mutually exclusive. You can have multiple processes performing non-blocking I/O, as a way of scaling over several cores without multithreading.
- bborud 13y agoExactly.
- jerf 13y ago"Why does the blog posting only mention fork and prefork as options?" Because this is a Linux kernel feature involving sharing a socket amongst multiple OS processes, and is therefore only interesting to talk about if you are using multiple OS processes. It's not a generalized primer on all techniques of handling IO.