php-src/sapi/roxen
Rasmus Lerdorf 76a2d2538c Heads up! I have moved the headers_only and response_code checks out of
SAPI and down into the individual SAPI modules.  I have made the
appropriate changes in all the SAPI modules, but please verify these.
The reason for this change is that Apache sometimes will feed PHP
a request_method of GET but have r->header_only set to true.  This happens
in an ErrorDocument redirect.  In this same scenario we want to preserve
the status code as well instead of just overwriting it with a 200 and
losing this information.  For now the other sapi modules act exactly as
before since they probably do not make this distinction, and they may
not even have a valid response code this early in the request.
@ Fix HEAD request bug on an Apache ErrorDocument redirect and preserve
@ the status code across the redirect as well.  (Rasmus)
2000-08-02 22:48:45 +00:00
..
config.m4 Removed obsolete, commented line 2000-06-12 23:41:34 +00:00
Makefile.in PRE_INCLUDES hack reverted 2000-06-06 00:02:03 +00:00
README Now recommend --enable-roxen-zts... 2000-03-02 22:13:24 +00:00
roxen.c Heads up! I have moved the headers_only and response_code checks out of 2000-08-02 22:48:45 +00:00
TODO Added another bug to be fixed 2000-06-06 16:18:09 +00:00

Roxen PHP support. Early version. Don't expect to be able to get it to
work. Requires Pike 0.7.79 and Roxen 1.4. Anything less won't work.

The module is now thread safe, in a couple of different modes. First
mode, the default, uses a process global PHP lock in the Roxen
module. This means that all PHP-requests are serialized (ie only one
script is executed at any one time). The second option is using ZTS
(Zend Thread Safe mode). Unless --enable-roxen-zts is specified, this
won't be used.

This solution now works fine and is recommended. Multiple PHP4
requests will be run in parallell. The maximum number of parallell
PHP4-execution is limited to the number of handle threads Roxen is
started with.

- The Author, David Hedbor <neotron@php.net>