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...
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com
Hi Stan,
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.
Cheers,
Hi!
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.
Ok, that makes sense, thanks.
--
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com
Hi!
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.Ok, that makes sense, thanks.
I don't know for sure but it should be possible to make it SAPI thing,
ie. it would be available everywhere. Right now it's just implemented
for CGI which lacked it the most. It's just about what path is passed
for looking for ini files to scan for. :)
Now that Marcus has implemented the conditional blocks for ini files, it
makes more sense to make this available always as you can enable
sections depending on current SAPI. (you can disable HOST sections if
current SAPI is CLI for example)
Anyone see any problems with this though? :)
--
Patches/Donations: http://pecl.php.net/~jani/
Hi Stan,
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!"