On 6 juil, 21:12, John <jspay...@verizon.net> wrote: > In my application I need to be able to overlap some processing, > collecting summary information from the database between HTTP > requests. If I start a thread and then return a HTTP response I > presume that the process that was serving the request will continue > until the thread completes. > This makes it very likely that the next > request from the same session will be assigned to a different > process. By associating a cache with the session I can populate the > cache with the results from the running thread and can set up some > sort of signal mechanism to indicate that the thread has completed. > > Is this design basically flawed for this environment? I seem to be > getting inconsistent results to the subsequent requests.
Looks like you want something like celery http://celeryproject.org/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
