- Httpdapy and Zope problems
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
On Sat, 12 Dec 1998, Grisha Trubetskoy wrote:
Although theoretically I don't see why Zope couldn't work with Httpdapy
^^^^^^^^ Httpdapy????
some day, it currently doesn't really, and here is why:
1. Because Apache runs multiple processes, BoboPOS databases will end up That's why all publisher serialize it to ONE LRP. 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 Not really. I've been using a pcgi published app with MANY threads and it works quite well :)
Andreas -- Win95: n., A huge annoying boot virus that causes random spontaneous system crashes, usually just before saving a massive project. Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS, Win 3.x, Win98.
participants (2)
-
Andreas Kostyrka -
Grisha Trubetskoy