> Apache duplicates 95% of what Zope's server does, so if you're only
> using Zope, then it's un-elegant to use Apache.
Not so - Apache is a mature production web server, Zope is an
application server that serves over HTTP, but it's HTTP server is *not*
designed for production use.
> the rewrite rules you have to throw at Apache are awkward
You may think so, but they are the supported, documented solution: -
> Zope can't handle cgi
That is because Zope is an application server, not a web server.
> I find the tokens "yourMailHost"
> and "yourDomain" terribly unclear.
I simply don't understand that. It's off topic, but here goes: -
My domain is "xfr.co.uk", and I have a mail host called "smtp" (because
that is what it serves). So, the token "yourMailHost" refers to the mail
host name and the "yourDomain" refers to the domain name, so to send me
mail, you make an SMTP connection to "smtp.xfr.co.uk".
What's the problem?
"Human language continually changes, innit."
- Stephen Juan
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -