Evan Phoenix 6777c771d8 Add separate IO reactor to defeat slow clients ... Previously, the app thread would be in charge of reading the request directly from the client. This resulted in a set of slow clients being able to completely starve the app thread pool and prevent any further connections from being handled. This new organization uses a seperate reactor thread that is in charge of responding when a client has more data, buffering the data and attempting to parse the data. When the data represents a fully realized request, only then is it handed to the app thread pool. This means we trust apps to not starve the pool, but don't trust clients.		2012-07-23 10:26:52 -07:00
..
puma	Add separate IO reactor to defeat slow clients	2012-07-23 10:26:52 -07:00
rack/handler	Added the ability to set RACK_ENV when Puma is called from a Rack app and not through the CLI	2012-07-05 22:07:45 +01:00
puma.rb	Remove non-required dirs from $LOAD_PATH	2012-01-08 16:48:51 -03:00