Hi,
I'd like to point out that as you've stated, django is deployed in
mulit-threaded environments successfully,
employing an app that makes use of geodjango in a multi-threaded environment
is not.
Justin (Bronn) will testify to this I'm sure (as I and others have run into
this issue whilst attempt
On Nov 17, 7:25 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
>
> That's just not true. At one point (two years ago?) it wasn't, but
> these days Django's deployed all over the place in mutli-threaded
> situations. If it wasn't threadsafe we'd hear about it.
>
As I understand it, there are
On Nov 17, 6:54 pm, Ludvig Ericson <[EMAIL PROTECTED]> wrote:
> On Nov 16, 2008, at 07:26, Chris wrote:
>
> > 3. Fear of multi-threading bugs shouldn't be a reason to avoid multi-
> > threading, especially when it could be very useful. We don't even know
> > if there are multi-threading bugs. And
On Mon, Nov 17, 2008 at 4:14 PM, matt westerburg <[EMAIL PROTECTED]> wrote:
> Is there any documentation as to why Django is not threadsafe? It just
> seems to me that with the Global Interpreter Lock and all, it would be
> threadsafe.
That wouldn't as nice as "really-really thread safe". You kn
On Mon, Nov 17, 2008 at 10:54 AM, Ludvig Ericson
<[EMAIL PROTECTED]> wrote:
> There are bugs. Django isn't thread-safe, and we know that.
Um...
That's just not true. At one point (two years ago?) it wasn't, but
these days Django's deployed all over the place in mutli-threaded
situations. If it w
Is there any documentation as to why Django is not threadsafe? It just
seems to me that with the Global Interpreter Lock and all, it would be
threadsafe. I don't intend to start a flame, I am just curious about
learning why this might be. I am favor of the mutlitprocess approach layed
out by Lud
On Nov 16, 2008, at 07:26, Chris wrote:
> 3. Fear of multi-threading bugs shouldn't be a reason to avoid multi-
> threading, especially when it could be very useful. We don't even know
> if there are multi-threading bugs. And even if there are, they can be
> fixed.
There are bugs. Django isn't t
The last thing new people need when they come in and start playing
around with the dev server is to worry about all the issues that can
come up with threading. I would never recommend to anyone who doesn't
really know what they're doing and anyone who does can easily use any
one of the number of s
I think I may have to actually agree that multi-threading is somewhat
needed, since it does limit these kind of features from working. I,
however, would deem it less a priority than most thing. If you can
write a patch for it (or if one exists, I didn't look) though, I don't
see any reason to not
On Nov 16, 5:21 pm, "Waylan Limberg" <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 16, 2008 at 1:26 AM, Chris <[EMAIL PROTECTED]> wrote:
> Especially considering there are already working solutions out there.
> I seem to recall at least one management command someone put together
> that runs a multit
On Sun, Nov 16, 2008 at 1:26 AM, Chris <[EMAIL PROTECTED]> wrote:
>
> I think http://code.djangoproject.com/ticket/3357 should be given
> another look at enabling optional multi-threading on the dev server.
> 3. Fear of multi-threading bugs shouldn't be a reason to avoid multi-
> threading, espec
Julian wrote:
> [...] I think some people want to use snippets like that [...]
Wouldn't you agree that's a pretty feeble use case for something as
potentially disruptive as multi-threaded serving? Particularly when the
CherryPy alternative is so readily available.
regards
Steve
--
Steve Holden
Some months ago I tried a snippet from djangosnippets.org which shows a
upload progress bar. I think some people want to use snippets like that and
a multi-threaded server would help you developing such applications.
2008/11/16 Vinay Sajip <[EMAIL PROTECTED]>
>
>
>
> On Nov 16, 6:26 am, Chris <[E
On Nov 16, 6:26 am, Chris <[EMAIL PROTECTED]> wrote:
> I thinkhttp://code.djangoproject.com/ticket/3357should be given
> another look at enabling optional multi-threading on the dev server.
>
> Jacob previously closed this ticket, noting the patch could introduce
> threading bugs, and would prov
I'm a bit confused how multi-threading has anything to do with AJAX?
Your requests will be slower, but they will still get processed (at
least I've never had any issues).
On Nov 16, 1:03 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> If the patch that's currently on there works with no chan
If the patch that's currently on there works with no changes at all,
I'd be hesitantly in favor of it, however if there any bugs, or other
complications associated with it, my answer is to use a real server,
setting up something like CherryPy locally is almost no effort, as
seen here:
http://www.
Does it need to be multi-threaded? Can you get a multi-process dev
server instead/also?
On Sun, Nov 16, 2008 at 1:26 AM, Chris <[EMAIL PROTECTED]> wrote:
>
> I think http://code.djangoproject.com/ticket/3357 should be given
> another look at enabling optional multi-threading on the dev server.
>
I think http://code.djangoproject.com/ticket/3357 should be given
another look at enabling optional multi-threading on the dev server.
Jacob previously closed this ticket, noting the patch could introduce
threading bugs, and would provide functionality too similar to that of
a production environm
18 matches
Mail list logo
