On Sat, 4 Apr 2009 00:53:31 -0700 (PDT)
Graham Dumpleton <graham.dumple...@gmail.com> wrote:
> There have been discussions about detection of client connection
> closing on the mod_wsgi list before. It is a far from simple problem.
> This is because it can only be detected at certain points,
> specifically when either reading data from client, or attempting to
> write it. If your code is some sort of blocking state, such as waiting
> for back end command to do something, this isn't a way you can get a
> notification that client has closed connection. Thus the command would
> have to do what it needs to first, and only when trying to write back
> data would you know. I think the threads on mod_wsgi list about this
> are:
That is actually a problem. My external command could spend a
considerable time without producing any output, so my approach fails to
detect a closed socket until data is actually being returned to the
client. I thought about trickling some sort of "heartbeat data" down
the line to the client while the external command is processing, but I
guess that won't work becuause of socket and/or apache buffers sitting
inbetween my webapp and the client.
Oh well... back to the drawing board. :-)
Thank you Graham and Malcom for your detailed answers!
Cheers,
Marcus
I
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
