On Thu, 12 Jul 2007 11:51:39 +0100, Lester Caine <[EMAIL PROTECTED]> wrote:
> chris# wrote:
>> Something just occurred to me that might satisfy both sides of the
> issue.
>> What about the way Apache handles their versions of Apache (1.x and
> 2.x).
>> That is to say; they haven't abandoned 1.3 (no surprise, as I think it
> still
>> has the biggest install base). They simply maintain security related
> issues.
>> ppl still continue to build modules for 1.3. ppl still continue to
> run/install it.
>> Apache doesn't hide it in some back corner. Everybody's happy. Would
> this
>> approach not be an acceptable "EOL" for PHP4?
>> Just a thought.
>
> But it does not get round the situation where people 'expect' PHP
> applications
> to RUN on PHP4 because PHP4 is available. Apache is a reasonable analogy,
> but
> there is a well defined divide between 1.x and 2.x installations and
> people
> developing for 2.x don't worry about 1.x. This division is not present in
> PHP
> so that even though PHP4 and PHP5 are different animals, the fact that a
> PHP5
> application CAN be fixed to run on PHP4 means that there is an expectation
> by
> some that it WILL. We need some final break with PHP4 so that this
> perception
> is broken and new development does not have to hark back to past history?
Wholly agreed. But I'm not sure I see a big (any) real difference here. For
example there are many similarities between 1.x and 2.x - even in the conf
file(s).
I have little difficulty cobbling a 1.x module out of a 2.x module. PHP5
never made any guarantee that PHP4 apps/classes/whatever would run in PHP5.
I don't know. Maybe I didn't phrase it right. In short; I not suggesting that
there be any /real/ change in the current/proposed/whatever "EOL";
Apache 1.3 is as stable as it's going to get.
PHP4 is as stable as it's going to get.
Apache 1.3 uncovers a security issue - Apache dev plugs it.
PHP4 uncovers a security issue - PHP dev plugs it.
Apache1.3 leads it's own life (without Apache 2.x).
PHP4 leads it's own life (without PHP5).
ppl continue to build modules for Apache 1.3 (without regard or care of Apache
2.x).
ppl continue to build and use PHP4 (without care or regard for PHP5).
Apache has a /huge/ install base.
PHP4 has a /huge/ install base.
Nobody "pitched a fit" when Apache 2 came out.
This is where I see the Apache "EOL" as it /could/ apply to PHP4.
This is how I see the parallel. So I thought it might be an easy solution
with little (or no) opposition (on either side of the fence).
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
> L.S.Caine Electronic Services - http://home.lsces.co.uk
> MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
> Firebird - http://www.firebirdsql.org/index.php
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
/////////////////////////////////////////////////////
Service provided by hitOmeter.NET internet messaging!
.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
