Re: [PHP4BETA] Installation quirk

From: Date: Tue, 01 Jun 1999 20:26:45 +0000
Subject: Re: [PHP4BETA] Installation quirk
References: 1 2 3 4  Groups: php.version4 
Request: Send a blank email to php-version4+get-1239@lists.php.net to get a copy of this message
On Tue, Jun 01, 1999 at 10:47:01PM +0200, Zeev Suraski wrote: > At 14:41 01/06/99 , Sascha Schumann wrote: > > > >To maintain backwards compatibility no version of PHP should claim x-httpd-php > >for itself. Using the version numbers in the MIME type to distinct between > >older and newer versions of PHP should make it easier for IPPs to provide > >even PHP version x and x+1. > > > >I don't think any provider will jump right on using PHP4. Experience tells you > >to wait before using any new major release in a production environment. This > >is true for all products, PHP4 will be no exception there. > > You can rarely run products side-by-side and migrate. You can't do it with > Apache. You can't do it with ftpd. You can't do it with mod_perl. You > can't do it with just about any server software. Because the mass of software does not allow parallel execution, we cannot do it either? That is like saying, because the major number of computers tend to crash daily, there must not be a single computer which has an uptime of more than two days. In a previous post you pointed out that "Hundreds of thousands of people still use Apache 1.2.x because upgrading to 1.3.x gives them no noticeable gain." I swear that you will convince these people to upgrade by providing what Apache is lacking so apparently. My point is that you will get more people testing PHP4, if you provide this parallal functionality. It is not a must, it is an additional feature which will make every admin happy. "Oh see, we can just put it on our machine and it will not conflict with our other software. We even can switch site by site over to PHP4." > The upgrade process in these environments is usually running the server on > another port, or on another machine that has access to the filesystem(s) in > question, configuring it as much as you can, testing it through a short > 'beta', and then going live. PHP should be no different. You always have > the CGI alternative, too. CGI is dog slow. So, while bogging down the web server with huge numbers of CGI instances, we either have to accept that a) PHP3 becomes even more slower or b) that the speed gain of Zend/PHP4 will simply vanish. Both scenarios are indiscutable for sites getting more than a few hits per minute. IPPs not wishing to be on the "bleeding-edge," and not wanting to risk to lose their customer base will wait until PHP 4 has been proven to be stable. For these sites it would be a big win, if it would be possible to provide PHP4 additionally without playing tricks (such as redirecting, moving sites to other hosts etc.). Again, it is an additional feature to maximise the size of the user base of PHP4 as soon as possible. More users, more testers, more bug reports, better code. And think of zend.com. > The fact that php3 became almost a 'brand name', and that the 3 became an > integral part of the name isn't a very good thing (and I'm probably to be > blamed the most for it, pushing the .php3 extension a couple of years > ago). Much like any other function or variable or name in any versioned > API I know doesn't include the version number embedded within, neither > should PHP. My comment was about the MIME-type used for the Apache module handler which is directly related to the technical side of the whole argument. Otherwise, I have no opinion of supporting PHP or PHPx as official brand name. -- Regards, Sascha Schumann Consultant

« previous php.version4 (#1239) next »