> And mod_wsgi has less performance/memory overheads than mod_python.
> One can't really compare mod_python andfastcgimemory usage as they
> have different ways of working. Performance comparisons are also
> difficult as which server is used and how it is configured can
> influence it.
>
> FWIW, i
On Jun 16, 11:22 pm, Florian Apolloner <[EMAIL PROTECTED]> wrote:
> I would stay with Apache, but I would drop mod_python in favor
> ofmod_wsgi[1].Mod_wsgiis pretty cool and written by the same person
> as mod_python and should be seen as it's successor.
The mod_wsgi code is not written by sam
I would stay with Apache, but I would drop mod_python in favor of
mod_wsgi [1]. Mod_wsgi is pretty cool and written by the same person
as mod_python and should be seen as it's successor. Btw WSGI is the
future for python web dev; so why not use it? There is even a page
about Django Integration [2]
James Matthews wrote:
Hi,
I am now debating on if i should use Apache with mod_python or
Lighttpd with fastcgi. I won't be serving many files (just one webpage
for now...) But that page will preform be doing many
calculation/database query's. Which one would you guys recommend. Pros
and Cons
Hi,
I am now debating on if i should use Apache with mod_python or Lighttpd with
fastcgi. I won't be serving many files (just one webpage for now...) But
that page will preform be doing many calculation/database query's. Which one
would you guys recommend. Pros and Cons
Thanks
James
--
http://s
5 matches
Mail list logo
