>>If so, how is it possible to embed a HTTP server (that spwans threads to run >>itself and to handle requests) inside an application?
An HTTP embedded server library is not a full HTTP server. >>nginx most definitely spawns threads when handling requests, how is that done >>in this kind of environment? I seem to recall that Nginx is configured for rump with a single process that does not fork but its been a while since I looked at that. If you did in to the nginx.conf provided with the tutorial you’ll probably find something that puts it in single process mode.
