Looks good enough for me, I don't see a problem with that.
On Wed, 2002-12-18 at 17:39, Shane Caraveo wrote:
> No. At the most, if anything, CLI should output an error message:
>
> if(getenv("GATEWAY_INTERFACE") != NULL) {
> printf("This is the PHP CLI binary, please configure your server to
> use the correct PHP CGI binary.");
> exit(1);
> }
>
> Xavier Spriet wrote:
> > Great.
> > In that case, in order to make things a little smoother for users, could
> > a little workaround like the one offered by Robin be considered ?
> >
> >
> >
> > On Wed, 2002-12-18 at 17:21, Andrei Zmievski wrote:
> >
> >>On Wed, 18 Dec 2002, Philip Olson wrote:
> >>
> >>>So every tutorial and documentation on this would have to
> >>>say this right?
> >>>
> >>> "Ask your sysadmin what the CGI and CLI versions of your
> >>> PHP are called, they could be anything as there is no
> >>> standard. For the purpose of this (tutorial|documentation),
> >>> we'll call CLI php-cli and CGI php-cgi."
> >>>
> >>>Same goes for all cgi scripts, they'll work some places but
> >>>not others... And various RPM's would have different naming
> >>>schemes depending on the maintainers preference.
> >>
> >>The merging of CLI and CGI will still happen, but in 4.3.1.
> >>
> >>-Andrei http://www.gravitonic.com/
> >>* Marriage is not a word. It's a sentence. Life-long sentence. *
--
Xavier Spriet <[EMAIL PROTECTED]>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
