Re: mod_python - Using Apache prefork Vs Apache worker

2006-09-08 Thread Niels
Hi there Just to report on this, i set up a machine with very little memory using apache 2.2.1 (worker mpm), with mod_python 3.3 (development version 20060520) and django. It seems there is nothing much in django nor python that isn't thread safe. External C libraries you load as a python module

Re: mod_python - Using Apache prefork Vs Apache worker

2006-09-07 Thread gabor
Graham Dumpleton wrote: > 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

Re: mod_python - Using Apache prefork Vs Apache worker

2006-09-07 Thread Graham Dumpleton
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

Re: mod_python - Using Apache prefork Vs Apache worker

2006-09-05 Thread gabor
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