Re: PHP_SAPI

From: Date: Mon, 20 Dec 1999 21:08:47 +0000
Subject: Re: PHP_SAPI
References: 1 2  Groups: php.dev 
Request: Send a blank email to php-dev+get-13883@lists.php.net to get a copy of this message
At 23:04 20/12/1999 , Sascha Schumann wrote:
On Mon, Dec 20, 1999 at 05:13:22PM +0200, zeev@zend.com wrote: The idea behind PHP_SAPI is bogus, as far as I can tell. We basically don't want the SAPI type to be hardcoded ANYWHERE in the PHP code (including info.c), and definitely not in the modules code (since we want just one binary for all of the different SAPIs). If we want the SAPI type to be detectable, it should be a part of the sapi_module_struct, which should be the only different structure between various PHP builds for different servers.
    The sapi_module_struct already contains such a thing. The
    name element is perfectly suitable for embedding the SAPI
    module name. I'll change the SAPI modules appropiately,
    info.c will display the SAPI module name then.
Cool. I should note that the original intention was that SAPI would be a library used not only by PHP, and the .name property in there should really read 'PHP', or 'FooBar', if FooBar is the app using SAPI. But IMO we won't be seeing any other SAPI apps in the near future, so you can use the .name property as the name of the SAPI server. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/

« previous php.dev (#13883) next »