This is precisely what unicorn is meant to do though, it's just a trope of the architecture to use hproxy on top. Calling fork() internally is ultimately akin

This is precisely what unicorn is meant to do though, it's just a trope of the architecture to use hproxy on top. Calling fork() internally is ultimately akin to what everyone is going to do. Why not use a library to do this and let that code gradually get tempered to a reliable status?