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? -- View this message in context: http://n2.nabble.com/How-do-you-signal-the-end-of-streaming-content-tp4934275p4935831.html Sent from the pylons-discuss mailing list archive at Nabble.com.
-- 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.
