Date | Commit message (Collapse) | ||
---|---|---|---|
2010-05-03 | doc: misc updates | ||
* avoid needless links to /Rainbows.html * keepalive_timeout has been 5 seconds by default for a while * update "Gemcutter" references to "RubyGems.org" | |||
2010-05-03 | doc: RDoc 2.5.x updates | ||
2009-12-22 | fix README speling fail | ||
2009-12-22 | README: add RevFiberSpawn | ||
2009-12-13 | README updates | ||
2009-12-13 | README: add Sunshowers reference | ||
2009-12-10 | README: HTML5 Web Sockets may not be supported, yet... | ||
2009-12-02 | add RevThreadPool to README | ||
2009-11-29 | doc: add NeverBlock to comparison and README | ||
2009-11-27 | README: switch rubyforge.org git links to repo.or.cz | ||
We've long had the repo.or.cz mirrors and RubyForge may not support git any longer. | |||
2009-11-27 | More documentation tweaks for the release | ||
2009-11-26 | README: formatting and updates | ||
2009-11-26 | README: "an HTTP", not "a HTTP" (I think...) | ||
We need a professional editor. | |||
2009-11-25 | Documentation updates for new concurrency models | ||
2009-11-25 | Gemcutter prep, fix RubyGems capitalization | ||
2009-10-26 | doc: Update TODO and README | ||
We have basic EventMachine and :async support. | |||
2009-10-19 | README: change ordering of concurrency model listing | ||
Revactor was our first take on the "rainbows" branch of Unicorn and probably less confusing to people that may have tracked that branch. ThreadPool was used in the "gossamer" branch of Unicorn before, but since this project is named Rainbows!, it's less logical. I'll freely admit to having some personal bias here and not being a fan of threads (and especially not pthreads!). | |||
2009-10-15 | README: link to AppPool and extra note about Rev model | ||
2009-10-15 | README: update with Rev model caveats | ||
2009-10-14 | README: update URLs | ||
2009-10-14 | documentation updates (mostly on network models) | ||
2009-10-12 | README: alter reply conventions for the mailing list | ||
Mailman is now configured to munge Reply-To: to point back to the mailing list. This might make things easier for folks on low traffic mailing lists like ours. | |||
2009-10-05 | doc: better "Rainbows!" RDoc examples and linkage | ||
2009-10-05 | Avoid naming names in LICENSE/README files | ||
Everything is logged in git anyways and it'll be easier to hand off to somebody else. | |||
2009-10-05 | summary: s/slow apps/sleepy apps/g | ||
I think "sleepy" is a better term than "slow" here. "slow" can mean apps that are CPU/memory bandwidth-bound, and Rainbows! sucks at those. | |||
2009-10-05 | README: add install instructions | ||
2009-10-05 | README: move RDoc links down to fix gem description | ||
2009-10-05 | huge documentation revamp | ||
2009-10-04 | doc updates; use "Rainbows!", not "Rainbows" | ||
Also add notes about development things and the configuration language which uses "Rainbows!". Calling ourselves "Rainbows!" will help us be taken even more seriously than if the project were just called "Rainbows" | |||
2009-10-04 | README: add pointers to the git repository | ||
2009-10-02 | initial revision | ||
No tests yet, but the old "gossamer" and "rainbows" branches seem to be basically working. |