aboutsummaryrefslogtreecommitdiff
path: root/www/rubygem-rack-timeout/pkg-descr
diff options
context:
space:
mode:
authorJoseph Mingrone <jrm@FreeBSD.org>2017-04-14 12:18:18 +0000
committerJoseph Mingrone <jrm@FreeBSD.org>2017-04-14 12:18:18 +0000
commitea0de7d06624b079d5bf21c63de1d05df9a49834 (patch)
tree828f787bc406a8429b375e53a5c2e76e223941fa /www/rubygem-rack-timeout/pkg-descr
parente8fd22852684068364c0666f38b857f16113cbf4 (diff)
downloadports-ea0de7d06624b079d5bf21c63de1d05df9a49834.tar.gz
ports-ea0de7d06624b079d5bf21c63de1d05df9a49834.zip
Notes
Diffstat (limited to 'www/rubygem-rack-timeout/pkg-descr')
-rw-r--r--www/rubygem-rack-timeout/pkg-descr9
1 files changed, 9 insertions, 0 deletions
diff --git a/www/rubygem-rack-timeout/pkg-descr b/www/rubygem-rack-timeout/pkg-descr
new file mode 100644
index 000000000000..ee1044df553a
--- /dev/null
+++ b/www/rubygem-rack-timeout/pkg-descr
@@ -0,0 +1,9 @@
+Rack::Timeout is middleware, which aborts requests that have been running for
+longer than a specified timeout.
+
+Rack::Timeout is not a solution to the problem of long-running requests, it is a
+debug and remediation tool. Developers should track rack-timeout's data and
+address recurring instances of particular timeouts, for example, by refactoring
+code so it runs faster or offsetting lengthy work to happen asynchronously.
+
+WWW: http://github.com/heroku/rack-timeout/