RE: [Zope] Can't build resource file for PCGI on Zope 2.7b1
From: Chris McDonough [mailto:chrism@zope.com] Subject: Re: [Zope] Can't build resource file for PCGI on Zope 2.7b1
On Mon, 2003-08-11 at 22:33, Jens Vagelpohl wrote:
Is PCGI being deprecated from Zope?
It is not receiving much attention anymore, to put it like that. With mechanisms like mod_rewrite and mod_proxy PCGI is almost never an appropriate solution anymore.
Yes, PCGI is being deprecated. Past 2.7 it will no longer available in the source distribution (nor in any binary distribution I'm aware of).
Hmmm...then I have a question. I've often seen statements like yours above that "[PCGI] is almost never an appropriate solution", but I'm still puzzled by something. For our needs, the fact that request to Zope can be redirected through a named pipe with PCGI (at least that is my understanding, we are in the process of setting this up right now) is very useful because we are looking at using Zope internally on our corporate intranet and the server will *NOT* be behind a firewall. By using a named pipe, it is much easier for us to direct access to the Zope server than if it were hanging off a port. Our current plan is to have iPlanent (not under my control) be the "front end" web server. The iPlanet server will be responsible for authentication. Then, the requests will be redirected to Zope using exUserFolder. Currently, the plan is to do this redirection through PCGI using named pipe. If PCGI is gone, how can we accomplish the same thing without opening up a port? I don't doubt that "[PCGI] is almost never an appropriate solution", but I cannot seem to figure out what is an appropriate solution in our case. Thanks for any help.
- C
-- Mike
If PCGI is gone, how can we accomplish the same thing without opening up a port? I don't doubt that "[PCGI] is almost never an appropriate solution", but I cannot seem to figure out what is an appropriate solution in our case.
Very simple if the frontend webserver sits on the same machine: Have Zope listen on a port on localhost only. Then your frontend server simply redirects/rewrites/whatever to that port on localhost. Thus Zope won't be reachable on any external interface. jens
participants (2)
-
Jens Vagelpohl -
Tiller, Michael (M.M.)