Re: [PHP4BETA] Installation quirk
| From: | Sascha Schumann | Date: | Tue, 01 Jun 1999 22:08:05 +0000 |
| Subject: | Re: [PHP4BETA] Installation quirk | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-1244@lists.php.net to get a copy of this message | ||
On Wed, Jun 02, 1999 at 12:00:21AM +0200, Zeev Suraski wrote:
> At 22:26 01/06/99 , Sascha Schumann wrote:
> >On Tue, Jun 01, 1999 at 10:47:01PM +0200, Zeev Suraski wrote:
> > > At 14:41 01/06/99 , Sascha Schumann wrote:
> > > >
> > >
> > > 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
>
> You said you don't see your ISP doing this upgrade. I pointed out that
> this sort of procedure is required for just about any other component in
> the server platform, so unless your ISP sucks, he does that sort of stuff
> anyway.
I'm focussing on extending the audience of PHP. To use your
terminology here, an IPP would suck, if he would force some new
product down his customer's throats without providing a 100%
backwards compatible solution.
Despite the claim that "[PHP4 is] so compatible we didn't even
bother to make them both run side by side," there will be bugs in
PHP4. There will be something which suddenly stops working in
contrast to PHP3.
Now, if my IPP would simply upgrade to PHP4 and my site would
crash, I would be a very unhappy customer. You cannot really test
for everything. The only real test is reality itself. And to use
one of Andrey's quotes here - "I wish life had an UNDO function."
> >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.
>
>
> My point is that there isn't a single program I've come across that has its
> major version number tagged on its functions or constants. A million
> coders are bound to be right. See below.
>
> > > 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.
>
> That's a myth. It simply is.
[some widely known things]
You really don't need to tell me what CGI is. I'm talking about
big sites which absolutely depend on PHP. Technical directors of
such companies would laugh at me, if I would suggest to them to
use CGI on their web servers.
> > 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
>
> As I said, (a) is pretty much insignificant except for a very very busy
> site, and (b) is simply baseless. The speed gain of PHP 4.0 doesn't come
> from a quicker startup, but from a blazing fast execution engine. In CS,
> CGI overhead is O(1), or in other words, pretty much insignificant.
Hm, well, if you would look at the second line above the
beginning of your last paragraph..
> > Both scenarios are indiscutable for sites getting more than a
> > few hits per minute
O(1) sounds great for a searching algorithm, but we are talking
about real life here. The overhead CGI creates (let alone lacking
features such as persistent database connections, a must for busy
sites) is not insignificant.
Scenarios:
- site A is an e-commerce site with millions of hits per day.
- site B has an extra PHP server hosting 500 domains of standard
clients, with a wide mix of different authors, scripting
techniques and so on.
Both scenarios have in common that they depend on PHP. Both could
gain advantage by using PHP4. Both are afraid of trying PHP4,
because it may not work for them (before you repeat the argument
"that PHP4 is compatible" now, read on).
They both cannot really test "on another port." But they would
both benefit from the possibility of driving PHP3 and PHP4
concurrently.
> >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.)
>
> They'd easily use the CGI. There are simply no reasons against it.
Yes, that is true for Joe Random User. It is blatantly wrong for
sites with "millions of hits," as you said yourself (I smell a
consensus here ;-).
> >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
>
>
> I do think of PHP 4.0's success as well as on zend.com. What I don't want
> to give people is the impression that PHP 3.0 -> PHP 4.0 requires a
> migration process, because it really doesn't. It's so compatible we didn't
> even bother to make them both run side by side (let alone the technical
> difficulties and ugliness of code we'd have to patch if we were to make
> them run side by side). And this isn't marketing crap, this is really how
> it is.
You forgot one important point. It is called reliability.
PHP4 is compatible by design. I simply accept that (and ignore
the "Incompatabilities" list in ZEND_CHANGES).
PHP4 is not compatible in the sense of using code which has been
proven to be stable on hundreds of thousands of web servers
world-wide.
I can easily demonstrate that - PHP4 crashes here when used as an
APXS module whereas PHP3 does not. Does the compatibility of the
scripting engine help me in this case? No.
--
Regards,
Sascha Schumann
Consultant