Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35490
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 64.233.184.236 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Hut9XHE49TrtHC46Y67+ClY94fJ+IXw3c4wy41iPS4LzUz7upkG2Sbo9P0A3nGweJIWeEt3Y+NpPpBXxz+1Lyr5DUzeuoXpKBnvJRMn3A/iUVDUhrOcs/eU+PSpg0VJSp0ZEOWa3u7LIuEg8T8XokfO5tsKHQzbwJNOclaCGBE0=
Message-ID: <10845a340802140145s6b11f602wf946b391bfe123da@mail.gmail.com>
Date: Thu, 14 Feb 2008 09:45:59 +0000
Reply-To: RQuadling@GoogleMail.com
To: "Pierre Joye" <pierre.php@gmail.com>
Cc: "Stanislav Malyshev" <stas@zend.com>, 
	"PHP Internals" <internals@lists.php.net>, 
	"Jani Taskinen" <jani@php.net>
In-Reply-To: <fe05d1540802131734sa2d09e6r79d2ff77a778c946@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47B390DD.7090403@zend.com>
	 <fe05d1540802131734sa2d09e6r79d2ff77a778c946@mail.gmail.com>
Subject: Re: [PHP-DEV] [HOST=] and [PATH=] cgi-only?
From: rquadling@googlemail.com ("Richard Quadling")

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!"