On Jun 21, 2011, at 8:32 AM, RVince wrote: > Perhaps a stupid question with an obvious answer -- my apologies in > advance if that is the case. I have "inherited" a pylons project, > wherein extremely lengthy calls to the controller are involved (i.e. > typically, when a controller method is invoked, it may rin for as long > as 8 hours, over millions of records.). Wondering what others here > would recommend for giving the user feeback on the status of the > processing until the new page is rendered, hours later. > > Any standard, pylons-ways of doing such? Thanks, RVince
I have no idea what the standard way of doing this is. We have a similar process in our project in which users can create potentially enormous Excel files. Sometime the file generation can take hours. We accept the request and put it in a queue. There is a queue runner which takes requests fires off a separate process to handle them. We then email the user with the URL for download when the file is read and have a page which shows the status of all Excel generation processes and allows for download there as well. If there is an error in the process the user is notified by email and the developers get an email as well with the stack trace and information to replicate the error. John Harrison -- 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.
