From 9d52bd0dd8a0d276f82560a05a1971c293bb432e Mon Sep 17 00:00:00 2001 From: Ian Bicking Date: Tue, 26 Jun 2007 17:28:28 +0000 Subject: docstring misformatting; added news link --- docs/paste-httpserver-threadpool.txt | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'docs/paste-httpserver-threadpool.txt') diff --git a/docs/paste-httpserver-threadpool.txt b/docs/paste-httpserver-threadpool.txt index afd1469..71ea81e 100644 --- a/docs/paste-httpserver-threadpool.txt +++ b/docs/paste-httpserver-threadpool.txt @@ -14,6 +14,7 @@ When a WSGI application is called, it's possible that it will block indefinitely. There's two basic ways you can manage threads: * Start a thread on every request, close it down when the thread stops + * Start a pool of threads, and reuse those threads for subsequent requests @@ -37,12 +38,18 @@ cases. The pool tracks all workers threads. Threads can be in a few states: * Idle, waiting for a request ("idle") + * Working on a request + - For a reasonable amount of time ("busy") + - For an unreasonably long amount of time ("hung") + * Thread that should die + - An exception has been injected that should kill the thread, but it hasn't happened yet ("dying") + - An exception has been injected, but the thread has persisted for an unreasonable amount of time ("zombie") -- cgit v1.2.1