I understand what you're saying, but I could've sworn I've seen Perl CGI scripts that forked something off from the web process that didn't hang the client up. Maybe I'm completely imagining that though (which is a distinct possibility).
On Dec 17, 6:44 pm, "Russell Keith-Magee" <[email protected]> wrote: > On Thu, Dec 18, 2008 at 7:55 AM, Greg Taylor <[email protected]> wrote: > > > Yeah, I was afraid this would be the case. The interval polling script > > was something I really wanted to avoid. > > > I can't believe this isn't possible, though. I assume this is a Django > > limitation of some sort? > > Ok, then. How would you do it in PHP? Rails? Any other web framework? > > The limitation here isn't Django per se. It is a fundamental design > contstraint of the web itself. HTTP essentially requires that all > requests can be satisfied very quickly. This pretty much eliminates > the possibility of having long-lived processing as part of request > handling. > > Strictly speaking, this isn't even a limitation of web applications. > Regardless of the programming paradigm, you shouldn't arbitrarily > start a long lived processing task. In order to give good UI feedback, > you should always start a long lived task in the background, and use > the foreground processing to monitor the status of the background > task. Web frameworks impose certain unique restrictions on the way > this pattern is realized, but the base requirements are fundamentally > the same as any other programming paradigm. > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
