about summary refs log tree commit homepage
path: root/README
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2009-10-09 15:24:05 -0700
committerEric Wong <normalperson@yhbt.net>2009-10-09 15:31:39 -0700
commitde9af3d5a2b378a9563066158eafe05d4c8c8a11 (patch)
treeda0a886da068cb895f2247928da81fad792f69f4 /README
parentb1b38756c6d8f93e2b9e0ffb154dd1c34900b06e (diff)
downloadunicorn-de9af3d5a2b378a9563066158eafe05d4c8c8a11.tar.gz
While Unicorn is one of very many Unix-only, pre-forking, shared
socket servers in existence, and Unicorn is _definitely_ not the
only server that only works *well* with fast clients, either.

But as far as we know, Unicorn is the first (and so far only)
server that emphasizes only working well with fast clients.
Diffstat (limited to 'README')
-rw-r--r--README8
1 files changed, 4 insertions, 4 deletions
diff --git a/README b/README
index 4d070a6..674d581 100644
--- a/README
+++ b/README
@@ -1,8 +1,8 @@
-= Unicorn: Rack HTTP server for Unix and fast clients
+= Unicorn: Rack HTTP server for fast clients and Unix
 
-Unicorn is a HTTP server for Rack applications designed to take
-advantage of features in Unix/Unix-like kernels and only serve fast
-clients on low-latency, high-bandwidth connections.  Slow clients should
+Unicorn is a HTTP server for Rack applications designed to only serve
+fast clients on low-latency, high-bandwidth connections and take
+advantage of features in Unix/Unix-like kernels.  Slow clients should
 only be served by placing a reverse proxy capable of fully buffering
 both the the request and response in between Unicorn and slow clients.