Documentation/comparison.haml in rainbows-0.7.0 vs Documentation/comparison.haml in rainbows-0.8.0

- old
+ new

@@ -83,17 +83,21 @@ %td.tee No %td.r18 Yes %td.r19 Yes %td.rbx No %td.slow Yes + %tr.comp_row + %td.mod RevThreadPool + %td.tee No + %td.r18 Slow* + %td.r19 Yes + %td.rbx No + %td.slow Yes %ul %li - RevThreadSpawn + 1.8 performance is being improved, follow - the - %a(href="http://rubyforge.org/mailman/listinfo/rev-talk") - rev-talk mailing list - for details. + RevThread* + 1.8 performance is bad with Rev <= 0.3.1. + Rev 0.3.2 (when it is released) should be much faster under 1.8. %li waiting on Rubinius for better signal handling %li rack.input streaming is what makes %a(href="http://upr.bogomips.org/") upload progress, @@ -178,10 +182,17 @@ %td.slowio %a(href="http://www.espace.com.eg/neverblock") NeverBlock, %a(href="http://rubyeventmachine.com") EventMachine %td.thr No %td.reent Yes + %tr.comp_row + %td.mod RevThreadPool + %td.slowio + thread-safe Ruby, + %a(href="http://rev.rubyforge.org/") Rev + %td.thr Yes + %td.reent No %ul %li Requirements for single thread reentrancy are loose in that there is no risk of race conditions and potentially mutually exclusive to @@ -274,9 +285,15 @@ %td.mod NeverBlock %td.devfd Yes %td.app_pool Yes* %td.lock Yes* %td.async NeverBlock, async_sinatra + %tr.comp_row + %td.mod RevThreadPool + %td.devfd Yes + %td.app_pool Yes + %td.lock Dumb + %td.async standard Ruby %ul %li "No!" means it's fundamentally incompatible, use an %a(href="Rainbows/AppPool.html") AppPool