Robert Pankowecki ???

/home/rupert/Dropbox/drug/wroclawrb/logos/drug-logo-name-rect-sq.png /home/rupert/Dropbox/drug/wroclawrb/krasnal.png /home/rupert/Dropbox/drug/arkency.png /home/rupert/Dropbox/Photos/rupert_outside_bw.jpg



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.


Async uploads

Handler for every language


  • standard


  • gem

Current status

Bright future

My motivations

Why not any other mongrel 2 gem ?


  • up to date with everything, even unreleased mongrel2 1.8
  • not use ffi-rzmq (JRuby)
  • no threads
  • too much code
  • ugly
  • should be like 10 gems

DRUG quality of code

Call for action:


  • IRC: on freenode