RE: [PHP-DEV] php-cgi vs php-cli naming issue

From: Date: Sun, 15 Dec 2002 17:46:09 +0000
Subject: RE: [PHP-DEV] php-cgi vs php-cli naming issue
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-92493@lists.php.net to get a copy of this message
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? John
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. So i am against comining them back. Besides that i fear that we would have to restart release cycle... marcus

« previous php.dev (#92493) next »