Apache does a perfectly adequate job, using very few resources, and it supports all the virtual hosts andother features that the site might be using for the zope content. It is certainly easier to have everything contained within Zope and the server that is front-ending zope. As for wanting to expose my kernel to the outside world with kernel-httpd (which I assume is an http daemon running in kernel space), I wouldn't even consider it. I don't like leaving even SSH and port 80 open. --sam J C Lawrence wrote:
On Mon, 24 Jan 2000 13:47:46 -0800 Jonothan Farr <jfarr@real.com> wrote:
If that's the case, the Local File System product will serve files from the local file system on the Zope server.
It's still in development but is fairly stable.
Not to slight this product (which is quite good), but it really doesn't make sense to be serving static content data from Zope or Apache, which are extremely heavy weight processes. Things like thttpd or kernel-httpd running on a high port are much lighter weight, much more performant, and do af ar better job of serving static content than their behemouth brethren.
-- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=--
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Sam Gendler Chief Technology Officer - Impossible, Inc. 1222 State St. Suite 250 Santa Barbara CA. 93101 w: 805-560-0508 f: 805-560-0608 c: 805-689-1191 e: sgendler@impossible.com