On Sun, 15 Dec 2002, Marcus Börger wrote: > At 18:33 15.12.2002, John Coggeshall wrote: > > >I see that renaming the CGI to php-cgi might break things indeed, and > > >that's never a good idea. But so is changing the name of the CLI (php) > > >to something else. It also breaks things, not only for me, but > > >also for > > >countless others using the CLI with the name 'php'. We also need to > > >think about these users as well. This leaves my opinion that i'm -1 on > > >renaming the CLI to something else, and i'm a -0 (yes this > > >changed :) on > > >renaming the CGI. This leaves the (IMO) only possible solution: > > >integrate them back into one binary and adding some magic > > >which triggers > > >CLI or CGI mode (perhaps to check for some environment variable). > > > >I'm a bit nervous about the checking of an environment variable thing. > >Is that platform/server independent? > > No, CGI is a well described standard. The only problem there is when > someone experiments with the combined executable as a CGI with > setting such vars and then forgets to remove the vars after testing is > done. In this case he has changed the behaviour of his CLI executable.
By environment variables I meant thing that get set for the CGI itnerface. From http://hoohoo.ncsa.uiuc.edu/cgi/env.html you can read that the GATEWAY_INTERFACE is available for all requests, so it's safe to test if this one exists. > So i am against comining them back. Besides that i fear that we would > have to restart release cycle... The release cycle would be a problem indeed... Derick -- ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ ------------------------------------------------------------------------- -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
