diff options
| author | ianb <devnull@localhost> | 2007-06-26 17:28:28 +0000 |
|---|---|---|
| committer | ianb <devnull@localhost> | 2007-06-26 17:28:28 +0000 |
| commit | 05136ba6a9ec63ea5cf8e5e84e118f92ea5b4339 (patch) | |
| tree | 3a9fedafff4fb37b16a7347eb7e96550260b3e8b /docs/paste-httpserver-threadpool.txt | |
| parent | 051a3a7ec175e043f1374a949214c640712e3120 (diff) | |
| download | paste-05136ba6a9ec63ea5cf8e5e84e118f92ea5b4339.tar.gz | |
docstring misformatting; added news link
Diffstat (limited to 'docs/paste-httpserver-threadpool.txt')
| -rw-r--r-- | docs/paste-httpserver-threadpool.txt | 7 |
1 files changed, 7 insertions, 0 deletions
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") |
