On Jan 23, 7:55 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> Keeping in mind the comments about possible thread-safety heisenbugs,
> let's make it so that the threaded behavior is *optional*, but people
> can turn it on if they're concerned about Ajax-induced stalling. What
> do you think? A
On 1/22/07, Graham King <[EMAIL PROTECTED]> wrote:
> Yes, it does. I telnet to 8000 to keep a request open, and make a
> regular browser request. With the current dev server the browser will
> hang until I kill the telnet. With the patch the browser responds.
>
> +1 from me.
>
> I'm going to
On 1/22/07, Istvan Albert <[EMAIL PROTECTED]> wrote:
>
> Jeremy Dunck wrote:
>
> > That said, most of the time, this is good stuff. Perhaps a management
> > option to turn it off?
>
> My understanding is that no part of basehttp.py is used when Django is
> deployed via modpython. If that is corre
Jeremy Dunck wrote:
> That said, most of the time, this is good stuff. Perhaps a management
> option to turn it off?
My understanding is that no part of basehttp.py is used when Django is
deployed via modpython. If that is correct then this addition would
make no difference in a production envi
On 1/22/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 1/22/07, Istvan Albert <[EMAIL PROTECTED]> wrote:
> > There is an easy way to turn on multi-threading for the default server,
> > see the diff below:
>
> Graham and/or anybody else who wants multi-threading in the
> development server,
Adrian Holovaty wrote:
> On 1/22/07, Istvan Albert <[EMAIL PROTECTED]> wrote:
>> There is an easy way to turn on multi-threading for the default server,
>> see the diff below:
>
> Graham and/or anybody else who wants multi-threading in the
> development server, can you try this patch and see whe
Adrian Holovaty wrote:
> Graham and/or anybody else who wants multi-threading in the
> development server, can you try this patch and see whether it solves
> your problem?
I updated my Django trunk with the ThreadingMixIn patch and looking at
a couple projects that have media served statically (f
On 1/22/07, Istvan Albert <[EMAIL PROTECTED]> wrote:
> There is an easy way to turn on multi-threading for the default server,
> see the diff below:
Graham and/or anybody else who wants multi-threading in the
development server, can you try this patch and see whether it solves
your problem?
Adri
There is an easy way to turn on multi-threading for the default server,
see the diff below:
Index: basehttp.py
===
--- basehttp.py (revision 4183)
+++ basehttp.py (working copy)
@@ -7,10 +7,16 @@
been reviewed for security issu
Howdy Graham,
> +1 for anything that makes the dev server multi-threaded. I'm hoping
> there might be a way to do this without introducing a dependency on
> CherryPy.
I believe the wsgiserver.py file from the CherryPy distribution is
independent from the rest of the framework. I know, for examp
I have also run up against the 1 connection limit on the dev server.
Particularly I was trying to get the server to make a connection to
itself to cache the output HTML of a template, so as to serve it as a
static file.
+1 for anything that makes the dev server multi-threaded. I'm hopi
Index: ../../django/django/core/management.py
===
--- ../../django/django/core/management.py (revision 4306)
+++ ../../django/django/core/management.py (working copy)
@@ -1136,6 +1136,65 @@
inner_run()
runserver.ar
I did a little tinkering and now have django running with the CherryPy
3.0 WSGI server for local development. I was quite surprised how easy
this was to do, essentially replacing in core/management.py:
>>> from django.core.servers.basehttp import run
>>> run(addr, int(port), handler)
with:
>>>
13 matches
Mail list logo
