Although theoretically I don't see why Zope couldn't work with Httpdapy some day, it currently doesn't really, and here is why: 1. Because Apache runs multiple processes, BoboPOS databases will end up being opened more than once. Since BoboPOS provides no other locking mechanism than "go away I'm busy" using UNIX file locking, you immediately run in to a "Resource Temporarily Unavailable" exception. 2. On Linux, apparently, there is a pretty serious low level problem with using LinuxThreads and Apache together. Zope has a Scheduler object which uses threads. LinuxThreads requires the use of a SIGUSR1 signal, and so does Apache. So when you create a new thread your whole web server hangs. P.S. Not to mislead the public - bare bones ZPublisher i.e. Bobo still works great, by the way, and is still by far my favorite way of writing WWW apps. Grisha