README in rainbows-5.1.1 vs README in rainbows-5.2.0
- old
+ new
@@ -1,6 +1,6 @@
-= Rainbows! - unicorn for sleepy apps and slow clients
+= Rainbows! - Rack app server for sleepy apps and slow clients
\Rainbows! is an HTTP server for sleepy Rack applications. It is based on
unicorn, but designed to handle applications that expect long
request/response times and/or slow clients.
@@ -49,11 +49,11 @@
== Features
* Designed for {Rack}[http://rack.github.io/], the standard for
modern Ruby HTTP applications.
-* Built on {Unicorn}[https://bogomips.org/unicorn/], inheriting its
+* Built on {unicorn}[https://bogomips.org/unicorn/], inheriting its
process/socket management features such as transparent upgrades and
Ruby configuration DSL.
* As with Unicorn, it is able to stream large request bodies off the
socket to the application while the client is still uploading. Since
@@ -79,11 +79,10 @@
* Comet
* BOSH (with slow clients)
* HTTP server push
* Long polling
* Reverse AJAX
-* real-time upload processing (via {upr}[http://upr.bogomips.org/])
\Rainbows! can also be used to service slow clients directly even with
fast applications.
== License
@@ -121,11 +120,11 @@
as well as the "\Rainbows!" block, so you can have the following in your
config file:
worker_processes 4 # assuming four CPU cores
Rainbows! do
- use :FiberSpawn
+ use :ThreadSpawn
worker_connections 100
end
See the {Rainbows! configuration}[link:Rainbows/Configurator.html]
{documentation}[link:Rainbows/Configurator.html]
@@ -134,26 +133,27 @@
== Development
You can get the latest source via git from the following locations
(these versions may not be stable):
- git://bogomips.org/rainbows.git
- git://repo.or.cz/rainbows.git (mirror)
+ https://bogomips.org/rainbows.git
+ https://repo.or.cz/rainbows.git (mirror)
You may browse the code from the web and download the latest snapshot
tarballs here:
* https://bogomips.org/rainbows.git
-* http://repo.or.cz/w/rainbows.git (gitweb)
+* https://repo.or.cz/rainbows.git (gitweb)
Inline patches (from "git format-patch") to the mailing list are
preferred because they allow code review and comments in the reply to
the patch.
We will adhere to mostly the same conventions for patch submissions as
-git itself. See the Documentation/SubmittingPatches document
-distributed with git on on patch submission guidelines to follow. Just
-don't email the git mailing list or maintainer with \Rainbows! patches.
+git itself. See the
+https://80x24.org/mirrors/git.git/tree/Documentation/SubmittingPatches?h=v2.20.1
+document distributed with git on on patch submission guidelines to follow.
+Just don't email the git mailing list or maintainer with \Rainbows! patches.
== Disclaimer
There is NO WARRANTY whatsoever if anything goes wrong, but let us know
and we'll try our best to fix it.