On Jan 18, 2011, at 7:39 AM, ae wrote: > > How do people deal with controller functions that take a long time? > (waiting for a subprocess or connection to another host, for example) > > It seems that while a thread is busy, anyone associated with the > thread can't use the application. I can see the benefit of this (one > user can't consume many threads) but I also need the application to be > responsive while a long-running request is being handled. > > In the past, I've handed requests off to another server (written on > Twisted) and had javascript poll for status, but this is a bit > laborious.
When you say "anyone associated with the thread", do you mean other requests using some shared, locked resource (like the session)? Or something else?
