|author||Eric Wong <email@example.com>||2009-10-17 16:02:24 -0700|
|committer||Eric Wong <firstname.lastname@example.org>||2009-10-19 11:02:25 -0700|
1 files changed, 15 insertions, 0 deletions
@@ -3,6 +3,13 @@
We're lazy and pick the easy items to do first, then the ones people
+* 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".
@@ -10,6 +17,12 @@ care about.
(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.
@@ -17,3 +30,5 @@ care about.
* Rubinius Actors - should be like Revactor and easily doable once
Rubinius gets more mature.
+* test and improve performance (throughput/latency/memory usage)