Event-driven handler

[Ryan Dahl]

> However, I'm not passing off the request via a socket -
> I'm running the code inside Nginx itself (it's written in C).
>
> I have the code running in a customized compiled Nginx binary, but
> currently the code is blocking (i.e. no other requests can be
> handled whilst my new code is being processed).  I'm looking to
> create a non-blocking version of my code, either through spawning
> off threads and handling each request in an isolated thread, or
> through some event-driven process.  I've not decided on that part of
> it yet, but I need to first get the code hooked into the event
> architecture of Nginx.

It sounds like you should make it into its own process and
communicating with it via an upstream module. You're not gaining
anything by compiling something like that into Nginx.