On Aug 5, 2007, at 11:46 PM, [EMAIL PROTECTED] wrote: > My question if about what is the best thing to do when some job > submitted to Web.py will take a ver long time. In my case, what I am > working on is uploading large files then processing within Python and > storing them in SQLite. The processing part is what really takes long, > possible up to an hour. One option I had been thinking about just > forking the process, the parent goes on to report to the user that > file was received correctly, while the child goes to perform the > processing in the background.
I think what you want is one of two functions in http.py: background or backgrounder. I haven't used either, so I'm not sure if there are any gotchas involved. -- Randall Randall <[EMAIL PROTECTED]> "[W]e ARE the market, this IS the market working, there's nothing external to be deferred to." -- Ian Bicking, on "let the market decide" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
