Re: [PHP-DEV] PHP 4.2.0 Release Announcement
On Tue, Apr 23, 2002 at 12:44:17AM -0500, Brian Foddy wrote: On Mon, 22 Apr 2002 18:56:28 -0700 (PDT), Rasmus Lerdorf wrote: As for Apache being at fault too, they very well could be. But the fact remains that PHP runs INSIDE Apache, and Apache starts fine without PHP, hence PHP must be at fault. Simply stating the obvious facts from the public point of view. Well, with that sort of logic we are completely screwed and might as well just give up. Public perception ranks very low on the priority list. 99.8% of users couldn't care less about Apache2 at this point. PHP 4.2 has been slow enough in coming. Holding it up longer for the .2% of users it might affect makes no sense. Those users can experiment with the snapshot releases. -Rasmus Ultimately, I'm just trying to look out for other PHP users, not me. People who don't follow these mailing lists. They see on the net that a new improved Apache is released. They check the PHP web site/freshmeat and see a new version that claims support for Apache, experimental tho it may be. So, i guess that you we're also amongst those people who used Linux kernel 2.4.0?? Apache 2.0.35 is the first 'official' release of Apache 2. I advise you to wait at least for Apache version 2.0.40.. In August PHP 4.3.0 comes out (according to the planning) and will have better support for Apache. But working with the CGI version of PHP works fine with Apache 2. Only the module version offen crashes. So they download both and start building. What do they get? Core dump. Usually before people will start opening trouble records or searching bug databases people will spend several hours re-rebuilding, double checking proceedures, etc, etc, etc. They've done everything correct. Its supposed to work, says right on the web page. Why does this core dump? I hope that people who're running Apache and programming PHP, know what they're doing.. They finally open a bug report only to have it immediately reply with... Yes, we know. What we really meant by 'Experimental' was it will core dump. That doesn't sound very good. Like i said, only the DSO version of PHP crashed with me. On IIS it's stable, on Apache 1.3.xx it's stable (You do know that apache is supporting more than 30 webservers right?!) If you want to use Apache 2 and PHP, than compile PHP as CGI-module and it will go fine.. -- With best regards, Dave Mertens, Development Manager [EMAIL PROTECTED] Innovative Solutions in Media BV Schiekade 101 3033 BG Rotterdam, Netherlands Tel. +31-10-2436060 Fax. +31-10-2436066 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] PHP 4.2.0 Release Announcement
If you want to reason why things were done was they were just check the archive. All your arguments have been brought up before. Apparently a decision was made (that does not match your perception). Best regards, Lukas Smith [EMAIL PROTECTED] ___ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de [EMAIL PROTECTED] ___ -Original Message- From: Brian Foddy [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 7:44 AM To: Rasmus Lerdorf Cc: PHP Developers Mailing List Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement On Mon, 22 Apr 2002 18:56:28 -0700 (PDT), Rasmus Lerdorf wrote: As for Apache being at fault too, they very well could be. But the fact remains that PHP runs INSIDE Apache, and Apache starts fine without PHP, hence PHP must be at fault. Simply stating the obvious facts from the public point of view. Well, with that sort of logic we are completely screwed and might as well just give up. Public perception ranks very low on the priority list. 99.8% of users couldn't care less about Apache2 at this point. PHP 4.2 has been slow enough in coming. Holding it up longer for the .2% of users it might affect makes no sense. Those users can experiment with the snapshot releases. -Rasmus Ultimately, I'm just trying to look out for other PHP users, not me. People who don't follow these mailing lists. They see on the net that a new improved Apache is released. They check the PHP web site/freshmeat and see a new version that claims support for Apache, experimental tho it may be. So they download both and start building. What do they get? Core dump. Usually before people will start opening trouble records or searching bug databases people will spend several hours re-rebuilding, double checking proceedures, etc, etc, etc. They've done everything correct. Its supposed to work, says right on the web page. Why does this core dump? They finally open a bug report only to have it immediately reply with... Yes, we know. What we really meant by 'Experimental' was it will core dump. That doesn't sound very good. That's a very frustrating scenario that will be occuring countless times probably right now. Why does PHP want to intentionally frustrate and turn off its own user community? What does that say about the PHP testing process and commitment to users? Now that 4.2 has been released and announced, the horse has left the barn. The only thing we can really do now is at least put a new note clearly on the web page stating that there is this problem with these two latest releases. Experimental, not for production just doesn't cut it. Not when we KNOW there is a definate problem, not some potential bug you might encounter. I've said my peace, Good night. Brian -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
On Tue, 23 Apr 2002, Brian Foddy wrote: That's a very frustrating scenario that will be occuring countless times probably right now. Why does PHP want to intentionally frustrate and turn off its own user community? What does that say about the PHP testing process and commitment to users? I was a little disenchanted when I started running into problems, and could be heard yelping yes, yes! when the topic first hit the list, but as the evening's progressed I've realized how much I'm taking for granted. We're talking about two major releases, each boasting many new features and improvements, but it's not as if we don't already have stable, well documented packages to use in production environments. Don't get me wrong, I'm as eager as the next geek is to upgrade, but for now I'm contented knowing that I'll be reaping the benefits in a few weeks' time. So far as the PHP dev-team and their commitment to users, I think it speaks pretty well -- when was Apache 2.0.35 released? We're pretty lucky to have as much support for Apache 2 as we do, given such a short amount of time. Regards, Tom Howell-Cintron thc/at/frognet/dot/net -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
I disagree whole heartedly. It doesnt look bad at all. From the public angle, it looks like the PHP Group are holding back on Apache 2 support until they can endorse its stability - but giving the PHP developers access to current research into the integration. If you want to play with with Apache 2, use the CVS HEAD. If you dont and you'd prefer a stable production enviroment, then use v4.2.0 [a fail to see any further issue]. In any case, I wasnt aware this list was [EMAIL PROTECTED] (or have I joined the wrong list again) - and Ive already spent 30 mins this morning just reading about your petty bickering Brian. -- Dan Hardiker [[EMAIL PROTECTED]] ADAM Software Systems Engineer First Creative Ltd Personally, I completely understand that is all new code and bugs will occur. I won't be going to Apache 2 for some time to come. The only reason I even tried it at all is I already was already getting requests on php-tuxedo for that combo so I thought I should give it a try. But I hope the Bugus link works well on the bug mailing list cuz you will probably be getting quite a few. And from the public perception it just looks bad. And that is my main point. It just looks bad. As for Apache being at fault too, they very well could be. But the fact remains that PHP runs INSIDE Apache, and Apache starts fine without PHP, hence PHP must be at fault. Simply stating the obvious facts from the public point of view. Brian On Mon, 22 Apr 2002, Rasmus Lerdorf wrote: That is exactly my point. I no more than read the encouraging report that its been identified and is close to a fix, and the next message says 4.2 has been released. It couldn't have waited just another week to get this fix in and tested? No, because it wouldn't make much of a difference. There will be other bugs. This is brand new code. Like I said, it will take a couple of months to stabilize. People should not be running Apache2+PHP in production yet. Any why exactly are you focusing on PHP here? Why not complain to the Apache folks about releasing Apache 2 before this was cleared up? This is not likely to be a PHP-specific bug and will require changes on both sides. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
You make it sound like it will core dump immediately for everyone. That's obviously not the case. It does work for most people. Well, for some anyway. Works fine on my test server, for example. On Tue, 23 Apr 2002, Brian Foddy wrote: So they download both and start building. What do they get? Core dump. Usually before people will start opening trouble records or searching bug databases people will spend several hours re-rebuilding, double checking proceedures, etc, etc, etc. They've done everything correct. Its supposed to work, says right on the web page. Why does this core dump? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] PHP 4.2.0 Release Announcement
I have Apache 2.0.25 with PHP 4.2.0RC2 running in production now. Been running since it was released. Billy Rose [EMAIL PROTECTED] -Original Message- From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 5:06 AM To: Brian Foddy Cc: PHP Developers Mailing List Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement You make it sound like it will core dump immediately for everyone. That's obviously not the case. It does work for most people. Well, for some anyway. Works fine on my test server, for example. On Tue, 23 Apr 2002, Brian Foddy wrote: So they download both and start building. What do they get? Core dump. Usually before people will start opening trouble records or searching bug databases people will spend several hours re-rebuilding, double checking proceedures, etc, etc, etc. They've done everything correct. Its supposed to work, says right on the web page. Why does this core dump? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] PHP 4.2.0 Release Announcement
Correction, 2.0.35 (typo) Billy Rose [EMAIL PROTECTED] -Original Message- From: Rose, Billy [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 6:20 AM To: 'Rasmus Lerdorf'; Brian Foddy Cc: PHP Developers Mailing List Subject: RE: [PHP-DEV] PHP 4.2.0 Release Announcement I have Apache 2.0.25 with PHP 4.2.0RC2 running in production now. Been running since it was released. Billy Rose [EMAIL PROTECTED] -Original Message- From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 5:06 AM To: Brian Foddy Cc: PHP Developers Mailing List Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement You make it sound like it will core dump immediately for everyone. That's obviously not the case. It does work for most people. Well, for some anyway. Works fine on my test server, for example. On Tue, 23 Apr 2002, Brian Foddy wrote: So they download both and start building. What do they get? Core dump. Usually before people will start opening trouble records or searching bug databases people will spend several hours re-rebuilding, double checking proceedures, etc, etc, etc. They've done everything correct. Its supposed to work, says right on the web page. Why does this core dump? -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
At 05:30 23/04/2002, Brian Foddy wrote: Experimental kinda implies that its at least usuable and might be fun to play with. Not recommending for production is a long ways from saying ohh, I guess it will coredump on startup... Experimental means experimental, and that it may very well crash on you on startup. Otherwise it would be labeled beta :) The fact PHP 4.2 got any support for Apache 2.0 at all was already bending the release cycle rules, delaying it further made little sense considering it would have still been labeled experimental, and considering the fact 4.2 already took a very long time to be released. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
- [EMAIL PROTECTED]% (Brian Foddy): So they download both and start building. What do they get? Core dump. Usually before people will start opening trouble [cut] with these two latest releases. Experimental, not for production just doesn't cut it. Not when we KNOW there is a definate problem, not some potential bug you might encounter. As Rasmus pointed out several times, this is generally not the case. After reading your posts to the list, i decided to do the build myself. Got a clean version of Apache 2.0.35 and a clean version of PHP 4.2.0. Built like a dream (well, since i'm having a fever at the moment, those dreams can be quite interesting). After making and configuring 2.0.35, the moment of truth had came. apachectl restart And voilá, i was running apache 2.0.35 with PHP 4.2.0 installed. I'm currently not running it compiled with any other options enabled, but saying that its doomed to coredump, is to exaggerate. Since some get it to run and some don't, there's obviously some sort of bugs still in there (and there'll probably always be), but hey, its experimental. I wasnt even hoping for this :-) -- mats -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
It didn't coredump for me on startup. Nor for I, and I've done quite a lot of testing on this thing. The startup error has been identified (even though not reproduceable by me for some reason) and I will supply a patch for that later today. There is still another bug (also nonreproduceable by me) that we have already spent much time on and hope to have solved soon. Brian, I suggest you join the volunteer effort by providing detailed bug reports or even patches to fix problems that you come across. Only then can you ensure that your issues are properly addressed. -aaron -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
On Tue, Apr 23, 2002 at 06:20:18AM -0500, Rose, Billy wrote: I have Apache 2.0.25 with PHP 4.2.0RC2 running in production now. Been running since it was released. Can you please describe your architecture (platform, os rev, etc...) and tell us what configure parameters you gave to both apache and php? Also, for anyone who has had problems getting this to work, please do the same. The two prevailing theories right now are: - php is tickling a broken pthread implementation. - there are some php/apache configure parameters that when combined can cause this. -aaron -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] PHP 4.2.0 Release Announcement
Apache 2.0.35: ./configure --with-so --prefix=/opt/apache-2.0.35 PHP 4.2.0RC2: ./configure --with-apxs2=/opt/apache-2.0.35/bin/apxs --with-mysql=/usr RedHat 7.1 HP LPr Dual PIII-850 RedHat 7.2 HP LPr Dual PIII-550 Billy Rose [EMAIL PROTECTED] -Original Message- From: Aaron Bannert [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 10:16 AM To: Rose, Billy Cc: PHP Developers Mailing List Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement On Tue, Apr 23, 2002 at 06:20:18AM -0500, Rose, Billy wrote: I have Apache 2.0.25 with PHP 4.2.0RC2 running in production now. Been running since it was released. Can you please describe your architecture (platform, os rev, etc...) and tell us what configure parameters you gave to both apache and php? Also, for anyone who has had problems getting this to work, please do the same. The two prevailing theories right now are: - php is tickling a broken pthread implementation. - there are some php/apache configure parameters that when combined can cause this. -aaron -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
Aaron Bannert wrote: It didn't coredump for me on startup. Nor for I, and I've done quite a lot of testing on this thing. The startup error has been identified (even though not reproduceable by me for some reason) and I will supply a patch for that later today. There is still another bug (also nonreproduceable by me) that we have already spent much time on and hope to have solved soon. Brian, I suggest you join the volunteer effort by providing detailed bug reports or even patches to fix problems that you come across. Only then can you ensure that your issues are properly addressed. -aaron If you look at the bug report (16475), you will see I did post a detailed followup to the original, stating both RC3 and RC4 had the same behavior. As for sumitting patches, I've done that too. Bug 9878 submitted in March 2001, but the included patch submitted with the bug report was only included in the last 4.1.2 (1 year turn around...) As for more detailed involvement, I could but any extra time I have I need to work towards php-tuxedo, which is a pretty large contribution to some users. Brian -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
Have you people lost it??? One of the MAJOR features is working with Apache2. But bug 16475 is still open and unresolved. Its been reported by several different people, all having the same effect. Why would you release this version until after this bug is closed and gone through at least one RC cycle. You will have lost a lot of credability from potential users if it core dumps the minute Apache 2 is started. PHP has usually always been very careful about major bugs in releases; until now. Brian On Mon, 22 Apr 2002 22:55:14 +0200 (CEST), Derick Rethans wrote: The PHP Group is happy to announce the immediate availability of PHP 4.2.0, the latest version of the widely-used, general-purpose scripting language that is especially well-suited for Web development. This latest release contains over one hundred changes, bug fixes and improvements over the previous release, PHP 4.1.2. Among the highlights are experimental support for Apache 2, cleanups in variable handling and overhauls of various PHP components, including the domxml, posix, sockets and iconv extensions. For more information, see below: - External variables The biggest change in PHP 4.2.0 concerns variable handling. External variables (from the environment, the HTTP request, cookies or the web server) are no longer registered in the global scope by default. The preferred method of accessing these external variables is by using the new Superglobal arrays, introduced in PHP 4.1.0. More information about this change: * PHP Manual: Predefined variables http://www.php.net/manual/en/html/language.variables.predefined.html * The PHP 4.1.0 release announcement http://www.php.net/release_4_1_0.php * Thomas Oertli's article on secure programming in PHP http://www.zend.com/zend/art/art-oertli.php Compatibility The Apache Software Foundation recently released their first General Availability version of Apache 2. PHP 4.2.0 will have EXPERIMENTAL support for this version. You can build a DSO module for Apache 2 with --with-apxs2. We do not recommend that you use this in a production environment. PHP 4.2.0 still lacks certain key features on Mac OS X and Darwin, and isn't officially supported by the PHP Group on these platforms. Specifically, building PHP as a dynamically loaded Apache module isn't supported at this time. PHP 4.3.0, due to be released in August, 2002, will be the first PHP release to officially support Mac OS X. It, along with future Mac OS X and Apache releases, will enable full feature parity with other PHP platforms. Improvements PHP 4.2.0 includes several improvements: * External variables (from the environment, the HTTP request, cookies or the web server) are no longer registered as global variables * Overhaul of the sockets extension * Highly improved performance with file uploads * The satellite and mailparse extensions were moved to PECL and are no longer bundled with the official PHP release * The posix extension has been cleaned up * iconv handling has been improved * Output buffering support, which was introduced in PHP 4.1.0 has been stabilized * Improved performance and stability of the domxml extension * New multibyte regular expression support * LOTS of fixes and new functions For a full list of changes in PHP 4.2.0, see the NEWS file (http://www.php.net/ChangeLog-4.php). regards, Derick Rethans [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
Apache 2 was released extremely quickly during the PHP 4.2 QA cycle. There really is no huge motivation to switch to Apache 2 right now. If the perchild mpm ever becomes stable it will be cool to use Apache 2 with PHP, but right now you are going to run into a whole lot of trouble with non-threadsafe libraries on UNIX machines. Basically we are still a couple of months away from any sort of production quality Apache/PHP combination, and this isn't just on the PHP side, it is on the Apache side as well. So please, take a breath, go have a beer and let us provide you with all this free code that will eventually solve all your problems. -Rasmus On Mon, 22 Apr 2002, Brian Foddy wrote: Have you people lost it??? One of the MAJOR features is working with Apache2. But bug 16475 is still open and unresolved. Its been reported by several different people, all having the same effect. Why would you release this version until after this bug is closed and gone through at least one RC cycle. You will have lost a lot of credability from potential users if it core dumps the minute Apache 2 is started. PHP has usually always been very careful about major bugs in releases; until now. Brian On Mon, 22 Apr 2002 22:55:14 +0200 (CEST), Derick Rethans wrote: The PHP Group is happy to announce the immediate availability of PHP 4.2.0, the latest version of the widely-used, general-purpose scripting language that is especially well-suited for Web development. This latest release contains over one hundred changes, bug fixes and improvements over the previous release, PHP 4.1.2. Among the highlights are experimental support for Apache 2, cleanups in variable handling and overhauls of various PHP components, including the domxml, posix, sockets and iconv extensions. For more information, see below: - External variables The biggest change in PHP 4.2.0 concerns variable handling. External variables (from the environment, the HTTP request, cookies or the web server) are no longer registered in the global scope by default. The preferred method of accessing these external variables is by using the new Superglobal arrays, introduced in PHP 4.1.0. More information about this change: * PHP Manual: Predefined variables http://www.php.net/manual/en/html/language.variables.predefined.html * The PHP 4.1.0 release announcement http://www.php.net/release_4_1_0.php * Thomas Oertli's article on secure programming in PHP http://www.zend.com/zend/art/art-oertli.php Compatibility The Apache Software Foundation recently released their first General Availability version of Apache 2. PHP 4.2.0 will have EXPERIMENTAL support for this version. You can build a DSO module for Apache 2 with --with-apxs2. We do not recommend that you use this in a production environment. PHP 4.2.0 still lacks certain key features on Mac OS X and Darwin, and isn't officially supported by the PHP Group on these platforms. Specifically, building PHP as a dynamically loaded Apache module isn't supported at this time. PHP 4.3.0, due to be released in August, 2002, will be the first PHP release to officially support Mac OS X. It, along with future Mac OS X and Apache releases, will enable full feature parity with other PHP platforms. Improvements PHP 4.2.0 includes several improvements: * External variables (from the environment, the HTTP request, cookies or the web server) are no longer registered as global variables * Overhaul of the sockets extension * Highly improved performance with file uploads * The satellite and mailparse extensions were moved to PECL and are no longer bundled with the official PHP release * The posix extension has been cleaned up * iconv handling has been improved * Output buffering support, which was introduced in PHP 4.1.0 has been stabilized * Improved performance and stability of the domxml extension * New multibyte regular expression support * LOTS of fixes and new functions For a full list of changes in PHP 4.2.0, see the NEWS file (http://www.php.net/ChangeLog-4.php). regards, Derick Rethans [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
FYI: The apache2 support in PHP is new and experimental. And in that bug report, one of the apache developers has already added a note that he's working on it so the fix will be in the next release. (PHP 4.2.1) Patience, please. --Jani On Mon, 22 Apr 2002, Brian Foddy wrote: Have you people lost it??? One of the MAJOR features is working with Apache2. But bug 16475 is still open and unresolved. Its been reported by several different people, all having the same effect. Why would you release this version until after this bug is closed and gone through at least one RC cycle. You will have lost a lot of credability from potential users if it core dumps the minute Apache 2 is started. PHP has usually always been very careful about major bugs in releases; until now. Brian On Mon, 22 Apr 2002 22:55:14 +0200 (CEST), Derick Rethans wrote: The PHP Group is happy to announce the immediate availability of PHP 4.2.0, the latest version of the widely-used, general-purpose scripting language that is especially well-suited for Web development. This latest release contains over one hundred changes, bug fixes and improvements over the previous release, PHP 4.1.2. Among the highlights are experimental support for Apache 2, cleanups in variable handling and overhauls of various PHP components, including the domxml, posix, sockets and iconv extensions. For more information, see below: - External variables The biggest change in PHP 4.2.0 concerns variable handling. External variables (from the environment, the HTTP request, cookies or the web server) are no longer registered in the global scope by default. The preferred method of accessing these external variables is by using the new Superglobal arrays, introduced in PHP 4.1.0. More information about this change: * PHP Manual: Predefined variables http://www.php.net/manual/en/html/language.variables.predefined.html * The PHP 4.1.0 release announcement http://www.php.net/release_4_1_0.php * Thomas Oertli's article on secure programming in PHP http://www.zend.com/zend/art/art-oertli.php Compatibility The Apache Software Foundation recently released their first General Availability version of Apache 2. PHP 4.2.0 will have EXPERIMENTAL support for this version. You can build a DSO module for Apache 2 with --with-apxs2. We do not recommend that you use this in a production environment. PHP 4.2.0 still lacks certain key features on Mac OS X and Darwin, and isn't officially supported by the PHP Group on these platforms. Specifically, building PHP as a dynamically loaded Apache module isn't supported at this time. PHP 4.3.0, due to be released in August, 2002, will be the first PHP release to officially support Mac OS X. It, along with future Mac OS X and Apache releases, will enable full feature parity with other PHP platforms. Improvements PHP 4.2.0 includes several improvements: * External variables (from the environment, the HTTP request, cookies or the web server) are no longer registered as global variables * Overhaul of the sockets extension * Highly improved performance with file uploads * The satellite and mailparse extensions were moved to PECL and are no longer bundled with the official PHP release * The posix extension has been cleaned up * iconv handling has been improved * Output buffering support, which was introduced in PHP 4.1.0 has been stabilized * Improved performance and stability of the domxml extension * New multibyte regular expression support * LOTS of fixes and new functions For a full list of changes in PHP 4.2.0, see the NEWS file (http://www.php.net/ChangeLog-4.php). regards, Derick Rethans [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
On Tue, 23 Apr 2002, Jani Taskinen wrote: FYI: The apache2 support in PHP is new and experimental. And in that bug report, one of the apache developers has already added a note that he's working on it so the fix will be in the next release. (PHP 4.2.1) Patience, please. Just by way of update, Aaron and I spent a lot of yesterday and today working on this. We've got it halfway fixed... it will start up without segfaulting now, but now it segfaults when shutting down the request. Ugh. Anyway, it's progress. Patch soonish I hope. --Cliff -- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
That is exactly my point. I no more than read the encouraging report that its been identified and is close to a fix, and the next message says 4.2 has been released. It couldn't have waited just another week to get this fix in and tested? Looking at the 4.2 announcement on the web page states... The Apache Software Foundation recently released their first General Availability version of Apache 2. PHP 4.2.0 will have EXPERIMENTAL support for this version. You can build a DSO module for Apache 2 with --with-apxs2. We do not recommend that you use this in a production environment Experimental kinda implies that its at least usuable and might be fun to play with. Not recommending for production is a long ways from saying ohh, I guess it will coredump on startup... Believe me, I'm a developer too, and I know the pressure (internal and external) to get a new release out. But this looks to me that with the much touted Apache 2 compatibility in this version, it could have waited just a little longer. Brian -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
That is exactly my point. I no more than read the encouraging report that its been identified and is close to a fix, and the next message says 4.2 has been released. It couldn't have waited just another week to get this fix in and tested? No, because it wouldn't make much of a difference. There will be other bugs. This is brand new code. Like I said, it will take a couple of months to stabilize. People should not be running Apache2+PHP in production yet. Any why exactly are you focusing on PHP here? Why not complain to the Apache folks about releasing Apache 2 before this was cleared up? This is not likely to be a PHP-specific bug and will require changes on both sides. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
Personally, I completely understand that is all new code and bugs will occur. I won't be going to Apache 2 for some time to come. The only reason I even tried it at all is I already was already getting requests on php-tuxedo for that combo so I thought I should give it a try. But I hope the Bugus link works well on the bug mailing list cuz you will probably be getting quite a few. And from the public perception it just looks bad. And that is my main point. It just looks bad. As for Apache being at fault too, they very well could be. But the fact remains that PHP runs INSIDE Apache, and Apache starts fine without PHP, hence PHP must be at fault. Simply stating the obvious facts from the public point of view. Brian On Mon, 22 Apr 2002, Rasmus Lerdorf wrote: That is exactly my point. I no more than read the encouraging report that its been identified and is close to a fix, and the next message says 4.2 has been released. It couldn't have waited just another week to get this fix in and tested? No, because it wouldn't make much of a difference. There will be other bugs. This is brand new code. Like I said, it will take a couple of months to stabilize. People should not be running Apache2+PHP in production yet. Any why exactly are you focusing on PHP here? Why not complain to the Apache folks about releasing Apache 2 before this was cleared up? This is not likely to be a PHP-specific bug and will require changes on both sides. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
As for Apache being at fault too, they very well could be. But the fact remains that PHP runs INSIDE Apache, and Apache starts fine without PHP, hence PHP must be at fault. Simply stating the obvious facts from the public point of view. Well, with that sort of logic we are completely screwed and might as well just give up. Public perception ranks very low on the priority list. 99.8% of users couldn't care less about Apache2 at this point. PHP 4.2 has been slow enough in coming. Holding it up longer for the .2% of users it might affect makes no sense. Those users can experiment with the snapshot releases. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
On Mon, 22 Apr 2002, Brian Foddy wrote: That is exactly my point. I no more than read the encouraging report that its been identified and is close to a fix, and the next message says 4.2 has been released. It couldn't have waited just another week to get this fix in and tested? Because we wait for everything, we never get any release out of the door. Apache 2 was released half-way through the Release Cycle, and it is itself not even stable yet. Actually, I dont see the big deal of this. Looking at the 4.2 announcement on the web page states... The Apache Software Foundation recently released their first General Availability version of Apache 2. PHP 4.2.0 will have EXPERIMENTAL support for this version. You can build a DSO module for Apache 2 with --with-apxs2. We do not recommend that you use this in a production environment Experimental kinda implies that its at least usuable and might be fun to play with. Not recommending for production is a long ways from saying ohh, I guess it will coredump on startup... It didn't coredump for me on startup. Believe me, I'm a developer too, and I know the pressure (internal and external) to get a new release out. But this looks to me that with the much touted Apache 2 compatibility in this version, it could have waited just a little longer. As I said, we can't wait for everything, and thus we need to to 'rush' our own development cycle because of others. Derick --- Did I help you? Consider a gift: http://www.amazon.co.uk/exec/obidos/registry/SLCB276UZU8B --- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Script Running Machine - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 4.2.0 Release Announcement
On Mon, 22 Apr 2002 18:56:28 -0700 (PDT), Rasmus Lerdorf wrote: As for Apache being at fault too, they very well could be. But the fact remains that PHP runs INSIDE Apache, and Apache starts fine without PHP, hence PHP must be at fault. Simply stating the obvious facts from the public point of view. Well, with that sort of logic we are completely screwed and might as well just give up. Public perception ranks very low on the priority list. 99.8% of users couldn't care less about Apache2 at this point. PHP 4.2 has been slow enough in coming. Holding it up longer for the .2% of users it might affect makes no sense. Those users can experiment with the snapshot releases. -Rasmus Ultimately, I'm just trying to look out for other PHP users, not me. People who don't follow these mailing lists. They see on the net that a new improved Apache is released. They check the PHP web site/freshmeat and see a new version that claims support for Apache, experimental tho it may be. So they download both and start building. What do they get? Core dump. Usually before people will start opening trouble records or searching bug databases people will spend several hours re-rebuilding, double checking proceedures, etc, etc, etc. They've done everything correct. Its supposed to work, says right on the web page. Why does this core dump? They finally open a bug report only to have it immediately reply with... Yes, we know. What we really meant by 'Experimental' was it will core dump. That doesn't sound very good. That's a very frustrating scenario that will be occuring countless times probably right now. Why does PHP want to intentionally frustrate and turn off its own user community? What does that say about the PHP testing process and commitment to users? Now that 4.2 has been released and announced, the horse has left the barn. The only thing we can really do now is at least put a new note clearly on the web page stating that there is this problem with these two latest releases. Experimental, not for production just doesn't cut it. Not when we KNOW there is a definate problem, not some potential bug you might encounter. I've said my peace, Good night. Brian -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
