On Thu, Apr 22, 2010 at 9:26 AM, Florin <[email protected]> wrote: > Maybe a solution would be to put more filters so the data won't be > that large and so it would eventually generate the pdf.
no, the solution is to put all the heavy work _out_ of the request/response cycle. just add the parameters (not the data) to an entry in a work queue and return with a redirect to another page that shows the task state and refreshes every few seconds (or poll with AJAX). meanwhile, a background daemon picks the task from the queue, and starts processing. if possible, make it write some progress info to the task entry, so the user can see it progressing. when it's finished, the status page sees the task as 'done' and redirects to the PDF download url. -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en.
