On Oct 1, 1:19 am, Chris Withers wrote:
> Torsten Bronger wrote:
> >> Why are you asking?
>
> > Can it be safely used with Apache's Worker MPM?
>
> I guess that would depend on a lot of things, not least of all whether
> you use mod_python ormod_wsgito deploy. Certainly
Torsten Bronger wrote:
>> Why are you asking?
>
> Can it be safely used with Apache's Worker MPM?
I guess that would depend on a lot of things, not least of all whether
you use mod_python or mod_wsgi to deploy. Certainly if it's the latter,
you're likely to get better help on the mod_wsgi
Yes, I wanted to know also if Django can be used with Apache's Worker
MPM?
I use it ( together with older Django version) but with problems.I
often receive
error
like this
if self.connection.get_server_info() >= '4.1':
InterfaceError: (0, '')
So I thought it could be a problem of
On Mon, Sep 28, 2009 at 4:34 AM, Torsten Bronger
wrote:
> Can it be safely used with Apache's Worker MPM?
The answer is, basically, "it depends on what *you*, the programmer, do".
The current stable releases of Django -- 1.0.3 and 1.1 -- don't by
themselves do
Hallöchen!
Chris Withers writes:
> Pythoni wrote:
>
>> Is Django thread safe?If so, from which version? Thanks for
>> reply
>
> The answer is most likely "no, but it doesn't matter".
>
> Why are you asking?
Can it be safely used with Apache's Worker MP
Pythoni wrote:
> Is Django thread safe?If so, from which version?
> Thanks for reply
The answer is most likely "no, but it doesn't matter".
Why are you asking?
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://
Is Django thread safe?If so, from which version?
Thanks for reply
L.
--~--~-~--~~~---~--~~
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@google
On Sat, Mar 29, 2008 at 3:52 AM, Graham Dumpleton
<[EMAIL PROTECTED]> wrote:
> The best I have ever been able to get out of anyone associated with
> Django development about thread safety is the comments by Jacob Kaplan-
> Moss in the following thread:
And that's really about the best anyone
Sorry, I forgot to post the url to the fastcgi docs
http://www.djangoproject.com/documentation/fastcgi/
On Mar 29, 7:52 pm, Eric <[EMAIL PROTECTED]> wrote:
> I currently use lighttpd and fastcgi, and I noticed that in the django
> documentation that they mention using threaded instead of
I currently use lighttpd and fastcgi, and I noticed that in the django
documentation that they mention using threaded instead of prefork when
running your fcgi server.
I had the same fears and I used prefork first, but after some load
testing of both, I decided to use threaded. I'm a brave soul
> The best I have ever been able to get out of anyone associated with
> Django development about thread safety is the comments by Jacob Kaplan-
> Moss in the following thread:
Sigh. Reading through that thread was singularly unsatisfying. I guess
that, for the moment, I'll have to stick with
The best I have ever been able to get out of anyone associated with
Django development about thread safety is the comments by Jacob Kaplan-
Moss in the following thread:
http://groups.google.com/group/django-developers/browse_frm/thread/905f79e350525c95/dfed56f8ed65aed2
Graham
On Mar 29,
Graham --
Thanks very much for your replies.
My concerns were from having two authorities saying different things
-- it makes the unwashed masses nervous. :-)
Of course, *now* I need to do a code review, since I hadn't been
thinking "thread safe" when I wrote it.
Is anyone (Django core
13 matches
Mail list logo