about summary refs log tree commit homepage
path: root/README
DateCommit message (Collapse)
2011-02-16README: clarify license terms and versions
Ruby 1.9.3dev switched to BSD but we remain under the same terms as the old Ruby 1.8 license. Mongrel2 exists now and also uses the BSD, so don't confuse people with that, either.
2011-01-21doc: git.bogomips.org => bogomips.org
bogomips.org is slimming down and losing URL weight :)
2011-01-20remove support for Sunshowers
The WebSocket protocol is still undergoing changes and unused. We won't waste time supporting it until it's finalized and doesn't break HTTP.
2010-12-27coolio*: favor Coolio over Rev
We still use and define Rev internally, but that's mostly just manual labor of converting stuff over.
2010-10-22README: update copyright year
This project is over 1 year old!
2010-08-10doc: it's always "Rainbows!" with a bang(!)
That is the official name of the project and we will not lead people to believe differently.
2010-06-21add Rainbows::Configurator module
Make it easier to link to the Rainbows! configuration documentation without anchors. This also reduces the amount of code we spew into Unicorn::Configurator.
2010-06-07README: update with Zbatery info
2010-05-29Rainbows! 0.93.0 - MOAR!!!1 v0.93.0
In our race to have more concurrency options than real sites using this server, we've added two new and fully supported concurrency models: WriterThreadSpawn and WriterThreadPool They're both designed to for serving large static files and work best with IO.copy_stream (sendfile!) under Ruby 1.9. They may also be used to dynamically generate long running, streaming responses after headers are sent (use "proxy_buffering off" with nginx). Unlike most concurrency options in Rainbows!, these are designed to run behind nginx (or haproxy if you don't support POST/PUT requests) and are vulnerable to slow client denial of service attacks. I floated the idea of doing something along these lines back in the early days of Unicorn, but deemed it too dangerous for some applications. But nothing is too dangerous for Rainbows! So here they are now for your experimentation.
2010-05-03doc: 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-03doc: RDoc 2.5.x updates
2009-12-22fix README speling fail
2009-12-22README: add RevFiberSpawn
2009-12-13README updates
2009-12-13README: add Sunshowers reference
2009-12-10README: HTML5 Web Sockets may not be supported, yet...
2009-12-02add RevThreadPool to README
2009-11-29doc: add NeverBlock to comparison and README
2009-11-27README: 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-27More documentation tweaks for the release
2009-11-26README: formatting and updates
2009-11-26README: "an HTTP", not "a HTTP" (I think...)
We need a professional editor.
2009-11-25Documentation updates for new concurrency models
2009-11-25Gemcutter prep, fix RubyGems capitalization
2009-10-26doc: Update TODO and README
We have basic EventMachine and :async support.
2009-10-19README: 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-15README: link to AppPool and extra note about Rev model
2009-10-15README: update with Rev model caveats
2009-10-14README: update URLs
2009-10-14documentation updates (mostly on network models)
2009-10-12README: 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-05doc: better "Rainbows!" RDoc examples and linkage
2009-10-05Avoid 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-05summary: 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-05README: add install instructions
2009-10-05README: move RDoc links down to fix gem description
2009-10-05huge documentation revamp
2009-10-04doc 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-04README: add pointers to the git repository
2009-10-02initial revision
No tests yet, but the old "gossamer" and "rainbows" branches seem to be basically working.