On 04/21/2010 01:12 PM, Mike Orr wrote:
On Wed, Apr 21, 2010 at 8:57 AM, Paweł Stradomski<[email protected]> wrote:
2010/4/21 jazg<[email protected]>:
Why would it prevent future requests if each request is a new thread?
I could manually create another thread for the job, but it seems like that
should not be necessary. I still don't understand why setting content-length
didn't work, did pylons decide to override that for some reason?
<snip>
There's also a ThreadPool.track_threads() method you can call to get a
summary of the server's state, although I don't know how you'd access
that method from a Pylons app.
Paste has a WatchThreads app that you can use to introspect a paste http server.
http://pythonpaste.org/modules/debug.watchthreads.html#module-paste.debug.watchthreads
- Shailesh
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
