Robert Pankowecki ???

/home/rupert/Dropbox/Photos/rupert_outside_bw.jpg /home/rupert/Dropbox/drug/arkency.png /home/rupert/Dropbox/drug/wroclawrb/krasnal.png

Mongrel2

Other servers assume that every request is received by a browser, then sent to a backend, and then directly sent out to the client and that’s it.
Mongrel2 assumes that there is a connected client, and it sends requests to backends, but it makes no assumptions about how those backends respond to the clients. All it requires is that the backend application send messages addressed to the client and it will write them on the socket.
Because of this design, Mongrel2 can easily house both classic HTTP clients, keep-alive style HTTP client, chunked encoding responses, JSSockets, or WebSockets using the same code.
out of request-replay ghetto (!!!)

target up to 128 connection with 1 message
Mongrel2 is the only web server capable of sending one request from a browser to N backends at once, and then return the replies from these handlers to M browsers. Not exactly sure what you could write with that, but it’s probably something really damn cool

ZeroMQ: a language- and transport-mechanism-agnostic messaging system that does not require a centralized messaging server to operate.
Using ZeroMQ lets Mongrel2 talk to a huge number of languages, operate within any kind of network architecture, and do it with a very simple communication model and API that most programmers can understand.
Your handler runs the application in different process.