From 4e7cab9f1727eccd90780d1ceb14948e0ace36a6 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Wed, 15 Jul 2015 22:03:53 +0000 Subject: doc: remove references to old servers They'll continue to be maintained, but we're no longer advertising them. Also, favor lowercase "unicorn" while we're at it since that matches the executable and gem name to avoid unnecessary escaping for RDoc. --- Application_Timeouts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'Application_Timeouts') diff --git a/Application_Timeouts b/Application_Timeouts index 5f0370d..561a1cc 100644 --- a/Application_Timeouts +++ b/Application_Timeouts @@ -4,10 +4,10 @@ This article focuses on _application_ setup for Rack applications, but can be expanded to all applications that connect to external resources and expect short response times. -This article is not specific to \Unicorn, but exists to discourage +This article is not specific to unicorn, but exists to discourage the overuse of the built-in {timeout}[link:Unicorn/Configurator.html#method-i-timeout] directive -in \Unicorn. +in unicorn. == ALL External Resources Are Considered Unreliable @@ -71,7 +71,7 @@ handle network/server failures. == The Last Line Of Defense The {timeout}[link:Unicorn/Configurator.html#method-i-timeout] mechanism -in \Unicorn is an extreme solution that should be avoided whenever +in unicorn is an extreme solution that should be avoided whenever possible. It will help catch bugs in your application where and when your application forgets to use timeouts, but it is expensive as it kills and respawns a worker process. -- cgit v1.2.3-24-ge0c7