Re: Application naming and project directory layout

On Thu, 26 Nov 2009 10:18:44 +0100 Marcus Weseloh <dja...@weseloh.cc> wrote: > [...] but are there other areas in Django that rely on > applications having unique names? Do I need to ditch the Python-style > namespacing and resort to module1_app1, module2_app1 application names? A

Application naming and project directory layout

Hi, I'm developing an application with several services/modules, every module is structured into several apps. I'm planning to use the following directory structure: project/ module1/ app1 (!) app2 app3 module2/ app1 (!) app4 app5 Both modules contain an

Re: Reacting to browser closing the socket

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, >

Re: Reacting to browser closing the socket

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

Re: Reacting to browser closing the socket

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

Reacting to browser closing the socket

Hi all, I'm using the code below to stream the response of an external command to the user. While that is all working fine, I would like to be able to react to the user closing the browser or hitting ESC by terminating the external process. When using the development server, I get a 'broken