| commit | 24248e78de684fbac374be216892a0b4050a1693 | |
| author | Eric Wong <normalperson@yhbt.net> | |
| Tue, 24 Nov 2009 09:50:26 +0000 (24 01:50 -0800) | ||
| committer | Eric Wong <normalperson@yhbt.net> | |
| Wed, 25 Nov 2009 06:51:48 +0000 (24 22:51 -0800) | ||
| tree | 0a5d9cb87fd23415a44b72c065770ff5e6a72c3a | treesnapshot (tar.gz zip) |
| parent | 9cc509bda610fa5ca8c642cdcf480835b8dfc468 | commitdiff |
rework RevThreadSpawn without TeeInput and 1.8 support
Exposing a synchronous interface is too complicated for too
little gain. Given the following factors:
* basic ThreadSpawn performs admirably under REE 1.8
* both ThreadSpawn and Revactor work well under 1.9
* few applications/requests actually need a streaming "rack.input"
We've decided its not worth the effort to attempt to support
streaming rack.input at the moment. Instead, the new
RevThreadSpawn model performs much better for most applications
under Ruby 1.9
Exposing a synchronous interface is too complicated for too
little gain. Given the following factors:
* basic ThreadSpawn performs admirably under REE 1.8
* both ThreadSpawn and Revactor work well under 1.9
* few applications/requests actually need a streaming "rack.input"
We've decided its not worth the effort to attempt to support
streaming rack.input at the moment. Instead, the new
RevThreadSpawn model performs much better for most applications
under Ruby 1.9
| lib/rainbows/ev_thread_core.rb | [deleted file] | blobblamehistory |
| lib/rainbows/rev_thread_spawn.rb | diffblobblamehistory | |
| t/GNUmakefile | diffblobblamehistory |