1 = TODO items for Rainbows!
3 We're lazy and pick the easy items to do first, then the ones people
6 * Improve test suite coverage. We won't waste cycles with puny
7 unit tests, only integration tests that exercise externally
10 * Rev + Thread - current Rev model with threading, which will give
11 us a streaming (but rewindable) "rack.input".
13 * EventMachine.spawn - should be like Revactor, maybe?
15 * Rev + callcc - current Rev model with callcc (should work with MBARI)
17 * Fiber support - Revactor already uses these with Ruby 1.9, also not
18 sure how TeeInput can be done with this.
20 * Omnibus - haven't looked into it, probably like Revactor with 1.8?
22 * Packet - pure Ruby, EventMachine-like library
24 * Rubinius Actors - should be like Revactor and easily doable once
25 Rubinius gets more mature.
27 * test and improve performance (throughput/latency/memory usage)