RE: [PHP-DEV] CGI and CLI
| From: | Xavier Spriet | Date: | Wed, 18 Dec 2002 20:53:03 +0000 |
| Subject: | RE: [PHP-DEV] CGI and CLI | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-92607@lists.php.net to get a copy of this message | ||
Experimental or not, people use it and have developed a need for it.
Many apps out there are based on experimental technology, that's not a
reason to break them all...
On Wed, 2002-12-18 at 15:48, Sebastian Nohn wrote:
> > -----Original Message-----
> > From: Sterling Hughes [mailto:sterling@bumblebury.com]
> > Sent: Wednesday, December 18, 2002 9:30 PM
> > To: Xavier Spriet
> > Cc: Andrei Zmievski; PHP Developers
> > Subject: Re: [PHP-DEV] CGI and CLI
> >
> >
> > > This note from Derick pretty much reflects the idea... it makes sense:
> > > <quote>
> > > 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).
> > > </quote>
> > >
> >
> > Hrmm, how does renaming php-cli break compatibility between PHP
> > _releases_?
>
> In no way! PHP-CLI always was marked as experimental.
>
> MfG, Sebastian
--
Xavier Spriet <xavier@wuug.org>