On 6/5/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > What's the issue or objective? Even if you push some bits down the > pipe, there's no guarantee the browser got them or rendered them > correctly. Maybe understanding your motivation would help provide a > useful answer. > > But, for a short answer, your view function will have returned before > Django starts pushing the bits. The redirect callback middleware > shows an example of handling a response in a special way based on an > exceptional condition (404 in that case), but I think you'd need to > implement something specific to the web server in order to > successfully detect that the other end of the connection was no longer > listening.
I've got an internal web app that, when given some special files, begins a code generation and compilation process. I update the status of the process by using some simple AJAX from the client side. What I'd like is that if the client closes their browser, some exception gets raised, and I can cancel the rest of the process on the server side. Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
