It doesn't need to be accessed in real-time, so you're totally right. I'm going to try a session key set by the loop as it iterates. That way ajax will know when the final iteration is done. Thanks!
On Jan 13, 8:23 am, Roy <royt...@gmail.com> wrote: > Is it dynamic data that needs to be accessed in real-time? If not, you > could cache it in your own database (using a cron job), so that the > view doesn't have to take too long. > > On Jan 13, 10:53 am, Adam Tucker <adam.j.tuc...@gmail.com> wrote: > > > I am working on a site where a page is loaded which replaces part of itself > > with another view using a simple ajax replacement (the load funciton in > > jQuery.) The view that is called iterates a loop anywhere from 3 to 10 times > > before getting to a render_to_response. Unfortunately, the view pulls data > > from a very slow source which I can't control, so a single interation can > > take up to 30 seconds to complete, and after 60 seconds it times out. I am > > looking for some pointers on ways that I could work around this, either by > > returning partial data at each iteration or some other method. Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
