2010/4/21 jazg <[email protected]>: > > It still waits for the cleanup to finish before ending the response. I think > that is basically the same as the __after__ controller method which is > already built in to pylons. I tried that and had the same problem. > > Isn't there a way to simply force the connection to close after my first > yield?
I don't think it's a good idea, even if it is possible. This way you are performing this long running action in worker thread/process, thus preventing it from servicing future requests until the task is done. Perhaps you should just launch another thread (or process, depending on server type) or use some messaging system to pass the job to some background process. -- Paweł Stradomski -- 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.
