I'm wondering how PCGI should be supported in Zope moving forward.
We currently have:
- A PCGI server in ZServer
- A pcgi directory that contains:
o A cgi program that is very thin and whos only job
is to forward requests to an app server running pcgi
o An unused PCGI publisher,
Jim Fulton wrote at 2003-2-13 11:30 -0500:
I'm wondering how PCGI should be supported in Zope moving forward.
Do we still need it?
I would prefer to drop it (to reduce complexity).
Dieter
___
Zope-Dev maillist - [EMAIL PROTECTED]
How about making it a separately downloadable
add-on like LocalFS, Squishdot, etc. etc.
--Craeg
Jim Fulton wrote at 2003-2-13 11:30 -0500:
I'm wondering how PCGI should be supported in Zope moving forward.
Do we still need it?
I would prefer to drop it (to reduce complexity).
Dieter
But mostly I thought PCGI (and FastCGI) was the preferred way, since it
is covered in detail in Zope's doc/WEBSERVER.TXT and neither mod_proxy
nor mod_redirect are mentioned in there. ;-)
Unfortunately thats more a matter of documentation inertia more than
anything. There are more articles on
Having only ever used Zope-behind-PCGI myself, if we drop it, what would
be the prevailing approach for running Zope behind Apache? Has everyone
switched to FastCGI (or Quixote's SCGI) but me?
Be aware that there are Zope-specific patches (some of which I provided)
in the version of PCGI that
Hi
I have always run Zope behind Apache utilising mod_proxy.
I have to admit I never tried or really even evaluated pcgi, and don't
build it when I install Zope.
Is there a benefit of pcgi over using mod_proxy ?
Rgds
Tim Hoffman
On Fri, 2003-02-14 at 09:16, Jeff Rush wrote:
Having only
[me]
AFAIK most people use Apache's mod_redirect to a Zope HTTP server
running at (e.g.) port 8000. No additional software needed.
I meant mod_proxy of course.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist -
Having only ever used Zope-behind-PCGI myself, if we drop it, what would
be the prevailing approach for running Zope behind Apache? Has everyone
switched to FastCGI (or Quixote's SCGI) but me?
AFAIK most people use Apache's mod_redirect to a Zope HTTP server
running at (e.g.) port 8000. No
I had thought (obviously incorrectly) that mod_proxy was hard to
configure correctly to pass all headers, particularly in complex virtual
hosting scenarios. But I'm no Apache expert.
And I thought that mod_redirect added overhead to every request, doing
the redirect cycle via the browser. It
