Just wrong for multi-threaded server, performing activities on behalf of lots of different principles. Server Models Server waits on a well-known port. Messages arrive and are routed to the application via accept. Server waits for the actual request. Server processes request.
Server sends response.
Process model Fork a new process for each request. Keep a pool of processes around and dispatch to them. Does not properly account for interrupt time resource consumption. A single task may require multiple applications. Can have a multi-threaded server and occasional outside processes.