Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6875
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <3FFDAA35.5020704@caraveo.com>
Date: Thu, 08 Jan 2004 11:06:29 -0800
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040107
MIME-Version: 1.0
To: Wez Furlong <wez@thebrainroom.com>
CC: PHP Internals List <internals@lists.php.net>
References: <20040108183103.GA21154@panix.com> <00c101c3d619$0ecb3230$8b018552@titan>
In-Reply-To: <00c101c3d619$0ecb3230$8b018552@titan>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] new win32 snapshot: changing .exe names
From: shane@caraveo.com (Shane Caraveo)

While I dont care if the name changes for php5, I dont buy the premise 
that more and more people will be using php outside the web.  I think 
cli has it's uses, but I think it will be a marginal group of people who 
make large use of it.
Shane

Wez Furlong wrote:

> If you need to configure php5 separately from php4, you're going to be
> editing your server config anyway, so (IMO at least) this is not an issue.
> 
> The CLI version should remain php.exe (this has been discussed before).
> 
> Consider the CGI name change a progressive one that will help avoid
> confusion with CLI and CGI (which were *both* named php.exe).  Now that
> PHP is expanding outside of the role of a webserver only language,
> more and more people will be using the CLI version of PHP especially
> now that win32 PHP is much more attractive for admin tasks (COM!)
> than it has been in previous releases.
> 
> The old style dir structure meant that you had to rename the CGI and
> then move the CLI out of a sub-directory in order to be able to use
> both CLI and CGI on the same box; clearly this is much more hassle
> to do for every snap than to change your server config only once :-)
> 
> --Wez.
> 
> 
>>Both the CGI and CLI exe's are now in the base directory.  CLI is called
>>"php.exe" and the CGI is called "php-cgi.exe."  Please consider reversing
>>the names.  Making the CLI "php-cli.exe" and the CGI "php.exe" will make
>>installation less of a hastle.
>>
>>Users and their computers expect the php.exe to be the CGI and are using
>>it to serve web pages.  While having each user individually change their
>>files isn't insurmountable, it's an unnecessary step for many thousands
> 
> of
> 
>>people.  And for some people, it's a step they'd need to repeat over and
>>over as they unzip new snapshots.
>>
>>By the way, thanks for renaming the dll.  I'm looking forward to running
> 
> 4
> 
>>and 5 concurrently as CGI's on my windows development system.
> 
>