From baac7113683af010b8e81f1f3df1d677f7101951 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 26 Oct 2009 18:53:24 -0700 Subject: doc: Update TODO and README We have basic EventMachine and :async support. --- README | 1 + TODO | 11 ++--------- 2 files changed, 3 insertions(+), 9 deletions(-) diff --git a/README b/README index e7bc0c7..81446e2 100644 --- a/README +++ b/README @@ -17,6 +17,7 @@ For network concurrency, models we currently support are: * {:ThreadPool}[link:Rainbows/ThreadPool.html] * {:Rev}[link:Rainbows/Rev.html]* * {:ThreadSpawn}[link:Rainbows/ThreadSpawn.html] +* {:EventMachine}[link:Rainbows/EventMachine.html] We have {more on the way}[link:TODO.html] for handling network concurrency. Additionally, we also use multiple processes (managed by Unicorn) for diff --git a/TODO b/TODO index 27ec5dd..8a47a37 100644 --- a/TODO +++ b/TODO @@ -7,18 +7,9 @@ care about. 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) @@ -28,6 +19,8 @@ care about. * Omnibus - haven't looked into it, probably like Revactor with 1.8? +* Packet - pure Ruby, EventMachine-like library + * Rubinius Actors - should be like Revactor and easily doable once Rubinius gets more mature. -- cgit v1.2.3-24-ge0c7