=======
modzope
=======

What is modzope?
----------------

modzope is an experimental module that connects the Zope 3 application
server to Apache 2.  This makes it possible to run a Zope 3
application within a regular Apache server and without Zope's own
server process.

modzope is built on top of mod_python, an Apache module that allows
one to handle Apache requests in Python.  modzope's key component is a
module that exposes mod_python functionality to a WSGI-compliant API,
which is combined with Zope 3's WSGI application support in the
modzope request handler.


Why on earth would one want to do this?
---------------------------------------

Apache is a well-known and proven webserver.  Its server backend has
proven to be stable and mature.  It is fast, scales well; Apache's
numerous add-on modules, such as mod_proxy and mod_ssl add invaluable
features to a web application.

Zope's zope.server is a custom component.  No tests so far have proven
it either stable or unstable, fast or slow, well or badly scaling. In
other words, there is an incalcuable uncertainty lying in that
component.  Furthermore, Zope2 history has shown that in serious
applications, one always uses Apache as a frontend to Zope in order to
gain more flexibility, caching controls and SSL capability.  Even
though this has proven to be fast, it is an unnecessarily complicated
setup with questionable indirection.


What's the status?
------------------

Experimental, but more than just a proof of concept.

Right now, it is possible to load a regular Zope 3 instance using
ZODB's FileStorage (regular Data.fs file) and access any URL.  It is
not yet possible to use ZEO.


Copyright
---------

modzope is copyrighted (c) 2005 by Philipp "philiKON" von
Weitershausen.  It is freely distributable under the terms of the Zope
Public License Version 2.1 (ZPL), as distributed with Zope 3.

wsgiref is copyrighted (c) 2004 by Philip J. Eby and may be
distributed under the terms of the PSF license (Python license) or the
ZPL.