Re: Reacting to browser closing the socket

2009-04-04 Thread Marcus Weseloh
On Sat, 4 Apr 2009 00:53:31 -0700 (PDT) Graham Dumpleton 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 readi

Re: Reacting to browser closing the socket

2009-04-04 Thread Graham Dumpleton
On Apr 4, 4:44 pm, Marcus Weseloh wrote: > Hi Malcom, > > thanks for your response! > > On Sat, 04 Apr 2009 12:21:11 +1100 > > Malcolm Tredinnick wrote: > > You're not really trying to solve a valid problem here. The > > development server isn't intended for streaming data or anything like > >

Re: Reacting to browser closing the socket

2009-04-03 Thread Marcus Weseloh
Hi Malcom, thanks for your response! On Sat, 04 Apr 2009 12:21:11 +1100 Malcolm Tredinnick wrote: > You're not really trying to solve a valid problem here. The > development server isn't intended for streaming data or anything like > that. It's a very simplistic server for basic stuff. So if y

Re: Reacting to browser closing the socket

2009-04-03 Thread Malcolm Tredinnick
On Sat, 2009-04-04 at 00:22 +0200, Marcus Weseloh wrote: > Hello again, > > I think I solved my problem (at least for the development server) by > monkey patching django.core.servers.basehttp.ServerHandler. Does > anybody know of any horrible side effects this might have, or can > suggest a more

Re: Reacting to browser closing the socket

2009-04-03 Thread Marcus Weseloh
Hello again, I think I solved my problem (at least for the development server) by monkey patching django.core.servers.basehttp.ServerHandler. Does anybody know of any horrible side effects this might have, or can suggest a more elegant solution? Thanks in advance, Marcus --- the monke