gabor wrote:
> Filipe wrote:
> > Hi,
> >
> > The docs say [1] that:
> > "Django requires Apache 2.x and mod_python 3.x, and you should use
> > Apache's prefork MPM, as opposed to the worker MPM."
> >
> > I want to test a Django site on a server (I plan to deploy there some
> > other sites in the future) where there are installed Apache 2 and
> > mod_python 3.1.4.
> >
> > I've seen some references [2][3] that make me suspect that the issues
> > that existed with mod_python and Apache worker might have been solved
> > in mod_python 3.2.8.
> >
> > What problems can I expect if I use mod_python 3.1.4?
> > Do you think the problems might have been fixed in 3.2.8?
> >
>
> well, generally, the "problem" with the worker MPM is that it's a
> multithreaded application.
>
> which means, that if you want to have your app in a worker MPM, it has
> to be thread-safe. and i don't know if django is thread-safe or not (i
> think it's not).
>
> also, when doing multithreaded python applications, the GIL (python's
> global interpreter lock) might become an issue.
>
> so, i'd recommend, that if you have enough  memory, use the prefork MPM.

If the inability to use worker MPM is because Django doesn't support
multithreading, then it would be impossible to use Django on Windows
as Apache there can only run with a multithreaded MPM, there is no
multi process option.

Although I have asked previously why it is said that the worker MPM
shouldn't be used, no one has yet given a definitive answer.

Also, saying the GIL might become an issue, this is no more than for
any other multithreaded application. One shouldn't be bringing the GIL
into this, as it has got nothing to do in practice with whether the
worker MPM can be used.

Graham


--~--~---------~--~----~------------~-------~--~----~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to