Re: [HOST=] and [PATH=] cgi-only?
| From: | Richard Quadling | Date: | Thu, 14 Feb 2008 09:45:59 +0000 |
| Subject: | Re: [HOST=] and [PATH=] cgi-only? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-35490@lists.php.net to get a copy of this message | ||
On 14/02/2008, Pierre Joye <pierre.php@gmail.com> wrote:
> Hi Stan,
>
>
> On Feb 14, 2008 1:52 AM, Stanislav Malyshev <stas@zend.com> wrote:
> > Hi!
> >
> > Do I understand correctly that current [HOST=] and [PATH=] functionality
> > for PHP works only for CGI/FCGI sapi? Is there any reason for other
> > SAPIs not to do it (except for the obvious - lack of implementation :)?
> > I know there's .htacess for Apache, etc. but there may be setups that
> > might prefer to deal with php.ini...
>
>
> We first discussed about fastcgi as a first step but the goal is to
> support this syntax in all SAPI (well, cli makes little sense). It was
> thought as a replacement for htscanner (see pecl) but without its
> limitation.
Whilst having HOST= may not make much sense for CLI, PATH= can be useful.
Say you have a live and test websites (either by HOST=test.domain.com
or PATH=C:\Sites\Test\Domain\public_html). The live site will have no
errors displayed. The test site will have them displayed (maybe).
For CLI having C:\Scripts\Live and C:\Scripts\Test is useful as this
will provide the same functionality as non CLI.
So, if you can please allow PATH= for CLI (rather than just assume it
is of no use and ignoring it).
I can't think of how I would use HOST= in CLI, unless maybe you could
get the machine's name (stretching for an idea here).
Thank you.
Richard.
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"