Network server paradigms (ctd)

Multiplexed IO

Generally single-process
The request/reply path is broken down into "chunks"
These chunks are generally on external boundaries
eg network IO, timed events
A main processing loop then checks for completed IO and calls the "next chunk"
Probably the fastest method currently for doing network services (in my knowledge)
Requires a _very strict programmer_, almost more so than threaded programming
Very easy to end up with "dangling bits" - requests that have closed unexpectedly but parts of other request still reference into the dead request
I bet squid still has some ..