mod_fastcgi version 1.3
Mark Brown (mbrown@OpenMarket.com)
Wed, 04 Sep 1996 22:24:02 -0400
Message-Id: <199609050224.WAA06474@breckenridge.openmarket.com>
To: fastcgi-developers@OpenMarket.com
Subject: mod_fastcgi version 1.3
Date: Wed, 04 Sep 1996 22:24:02 -0400
From: Mark Brown <mbrown@OpenMarket.com>
mod_fastcgi version 1.3 is now available from
http://www.fastcgi.com/servers/apache/1.3/apache-fastcgi.tar.Z
(the index page won't point to this version until some time tomorrow,
so you need the URL.)
This module has been improved quite a bit; if you are using the
old one I urge you to try the new one. Here is the list of
changes from the README file:
* * * * *
1. Module sometimes busy-waited in FastCgiDoWork. Fixed.
2. Module violated the Apache buff abstraction.
Fixed. Might now work with SSL (not tested).
As part of the fix, eliminated support for
Apache 1.0x versions.
3. Module failed to chmod the Unix domain listening sockets
it created, so protections were set according to the current
umask. Fixed.
4. Module forked too many process manager processes: One
per AppClass. When the Apache parent ran as root, these
process manager processes ran as root. New process
manager is a single process (only started if AppClass is
used) and runs with same privileges as other children.
The new process manager doesn't do any polling, so
there's less system overhead than before.
5. AppClass insisted on getting at least two arguments. Fixed.
6. Module used setjmp/longjmp, causing compiler warnings
on some platforms (e.g. Linux.) The module no longer
uses setjmp/longjmp.
7. Module created listening sockets in /tmp, where they were
sometimes wiped out by cleanup scripts. Added FastCgiIpcDir
directive to give control over the location of listening
sockets.
8. Module wrote error log entries without a timestamp. Fixed.
9. AppClass directive wrote error messages to stderr in addition
to returning a char * message to the Apache core. Fixed.
* * * * *
Thanks to everyone who reported bugs and made suggestions.
--mark