[Zope] Zope port and provider

[Mike Renfro]

On Tue, Nov 27, 2001 at 04:41:36PM +0100, James van der Veen wrote:

> "There appears to be a serious flaw with zope:  one needs a zope provider.
> and there aren't too many.  apparently zope grabs port 80 and keeps it.  is
> this true? are there workarounds so that any isp will do?"

Not true on unilaterally grabbing port 80. It'll grab whatever port
you tell it to (and doesn't default to port 80), and you can
selectively enable/disable Zope's http, ftp, and webdav services.

Some (like me) run Zope as a separate process listening on a
high-numbered port, then use Apache or Squid as a proxy server to
direct particular requests (or all requests) to the Zope process. A
provider that gives you shell access or at least the ability to run
your own daemons, and a bit of tweaking to the section of their
httpd.conf is all that's required. You can avoid the httpd.conf
tweaking if you don't mind having URLs with ugly port numbers in them.

Some use the PCGI method of running Zope, which should work with any
web server that does PCGI (definitely Apache, and probably IIS). Don't
know if there's any reduction of effort on this compared to the
previous solution.

The insane (or those who expect almost zero Zope traffic) run Zope as
a regular CGI, instead of as a persistent CGI. Any provider that lets
you upload your own CGIs should be compatible with this, but it'd be
incredibly slow under load.

-- 
Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University -- renfro@tntech.edu