It wouldn't need a pool of threads for a stack, it just needs some memory in the server's address space for the stack. Together with the other points about mar

It wouldn't need a pool of threads for a stack, it just needs some memory in the server's address space for the stack. Together with the other points about marking the current thread sleeping and passing control to the server thread, and about server threads waiting for an invocation, I think what is described is pretty clearly the server threads are being used to execute code on the server on behalf of the client request.