1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
| | = TODO items for Rainbows!
We're lazy and pick the easy items to do first, then the ones people
care about.
* Improve test suite coverage. We won't waste cycles with puny
unit tests, only integration tests that exercise externally
visible parts.
* (maybe) make our tests TAP-compatible. Unfortunately the the
only shell library we've seen for TAP seems to use bashisms.
* Rev + Thread - current Rev model with threading, which will give
us a streaming (but rewindable) "rack.input".
* EventMachine - much like Rev, but we haven't looked at this one much
(our benevolent dictator doesn't like C++). If we can figure out how
to do Rev without Revactor, then this should be pretty easy.
* EventMachine + catch/throw :async API used in Thin
* EventMachine.spawn - should be like Revactor, maybe?
* Rev + callcc - current Rev model with callcc (should work with MBARI)
* Fiber support - Revactor already uses these with Ruby 1.9, also not
sure how TeeInput can be done with this.
* Omnibus - haven't looked into it, probably like Revactor with 1.8?
* Rubinius Actors - should be like Revactor and easily doable once
Rubinius gets more mature.
* test and improve performance (throughput/latency/memory usage)
|