Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-22 Thread Rasmus Lerdorf
On Thu, 22 Aug 2002, Kristian Koehntopp wrote: > Am Donnerstag, 22. August 2002 09:43 schrieb Rasmus Lerdorf: > > Putting in locks is the easy part. The tough part is finding > > which libraries are safe and which ones aren't. > > I think that is easy, too. Either the library you are using is >

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-22 Thread Kristian Koehntopp
Am Donnerstag, 22. August 2002 09:43 schrieb Rasmus Lerdorf: > Putting in locks is the easy part. The tough part is finding > which libraries are safe and which ones aren't. I think that is easy, too. Either the library you are using is being documented as threadsafe, then it is. Or it isn't d

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-22 Thread Sebastian Bergmann
Shane Caraveo wrote: > Rasmus Lerdorf wrote: >> But how do you propose we come up with perfect Apache 2.0 support? > > FastCGI :) What's the status of Apache 2.0's FastCGI filter / module? Where can it be found? -- Sebastian Bergmann http://sebastian-bergmann.de/ http://

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-22 Thread Zeev Suraski
At 23:09 21/08/2002, Shane Caraveo wrote: >Rasmus Lerdorf wrote: >>But how do you propose we come up with perfect Apache 2.0 support? > >FastCGI :) Sounds like a plan (seriously) Zeev -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-22 Thread Rasmus Lerdorf
Putting in locks is the easy part. The tough part is finding which libraries are safe and which ones aren't. You can't really test for it as thread bugs tend to be subtle, occur sporadically and get worse with load. So who are we going to trick into testing this stuff for us on their loaded prod

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-22 Thread Sterling Hughes
> Am Mittwoch, 21. August 2002 22:09 schrieb Shane Caraveo: >> Rasmus Lerdorf wrote: >> > production quality. The best we can do is pick a small set >> > of extensions and a small set of platforms and say that with >> > the limited set of extensions, against a specific set of >> > versions

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-22 Thread Kristian Koehntopp
Am Mittwoch, 21. August 2002 22:09 schrieb Shane Caraveo: > Rasmus Lerdorf wrote: > > production quality. The best we can do is pick a small set > > of extensions and a small set of platforms and say that with > > the limited set of extensions, against a specific set of > > versions of addon libra

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Pierre-Alain Joye
On Wed, 21 Aug 2002 16:37:13 -0400 (EDT) Dan Kalowsky <[EMAIL PROTECTED]> wrote: > On Wed, 21 Aug 2002, Pierre-Alain Joye wrote: > > > Works well in 4.1.1 : > > > > on : SunOS argiope 5.8 Generic_108528-05 sun4u sparc SUNW,Ultra-250 > > You are the first to report back that I've seen/heard from

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Dan Kalowsky
On Wed, 21 Aug 2002, Pierre-Alain Joye wrote: > Works well in 4.1.1 : > > on : SunOS argiope 5.8 Generic_108528-05 sun4u sparc SUNW,Ultra-250 You are the first to report back that I've seen/heard from stating it works. You're even on one of the two major difficulty platforms. Now try using 4.2

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Shane Caraveo
Rasmus Lerdorf wrote: > But how do you propose we come up with perfect Apache 2.0 support? FastCGI :) > If we > limit it to the pre-fork mpm, we can probably get quite close to perfect > stability, but for any of the threaded mpms we are completely at the mercy > of the threadsafetyness of all

RE: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Adam Maccabee Trachtenberg
I am willing to accept this. I don't think it's the job of the PHP group to fix thread-safetyness for all libraries on all platforms. That's a herculean task. Plus, I'm sure we're not alone in problem. Surely the mod_perl folks and [insert your favorite popular Apache module here] have similar iss

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Pierre-Alain Joye
On Wed, 21 Aug 2002 15:46:50 -0400 (EDT) Dan Kalowsky <[EMAIL PROTECTED]> wrote: > On Wed, 21 Aug 2002, Shane Caraveo wrote: > > > It should simply be marked EXPERIMENTAL, but not removed. On the other > > hand, it doesn't have to be included in the distribution if it simply > > does not work c

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Pierre-Alain Joye
On Wed, 21 Aug 2002 09:04:21 -0400 (EDT) Dan Kalowsky <[EMAIL PROTECTED]> wrote: > Adding to the ever expanding list... > o Decide if we are or are not going to support the iPlanet system. If we > are, it needs to be drastically fixed, if we're not we need to drop it. > Really. Look at the bu

RE: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Rasmus Lerdorf
But how do you propose we come up with perfect Apache 2.0 support? If we limit it to the pre-fork mpm, we can probably get quite close to perfect stability, but for any of the threaded mpms we are completely at the mercy of the threadsafetyness of all the various third party libraries on all the v

RE: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Adam Maccabee Trachtenberg
On Wed, 21 Aug 2002, Zeev Suraski wrote: > I think that at this point we should switch from wish-list mode, to > a down-to-earth realistic mode. That is, not put everything that we > want to see in the roadmap, but only things which are either > pre-requisites or things we know with a great deal

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Dan Kalowsky
On Wed, 21 Aug 2002, Shane Caraveo wrote: > It should simply be marked EXPERIMENTAL, but not removed. On the other > hand, it doesn't have to be included in the distribution if it simply > does not work correctly. It's apparently been broken since 4.0.5. I did a little bit of patching it up so

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Shane Caraveo
> > > > o Decide if we are or are not going to support the iPlanet system. If we >are, it needs to be drastically fixed, if we're not we need to drop it. >Really. Look at the bug reports. > > It should simply be marked EXPERIMENTAL, but not removed. On the other hand, it doesn't have to be i

RE: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Zeev Suraski
At 17:55 21/08/2002, Joseph Tate wrote: >o Rewrite the ISAPI IIS interface. "Gasp". From the ground up, or find >some other way to fix bug #15333. The work arounds listed in the bug report >are not acceptable in production systems, just as temporary stop-gap methods >for developing new applicat

RE: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Joseph Tate
And a couple more things. > Adding to the ever expanding list... > > On Wed, 21 Aug 2002, Sterling Hughes wrote: > > > > Hi all, > > > > > > Following on from the recent debug_backtrace discussion, and the > > > discussion about just what we are releasing next and so on, I'd just > > > thought I

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Dan Kalowsky
Adding to the ever expanding list... On Wed, 21 Aug 2002, Sterling Hughes wrote: > > Hi all, > > > > Following on from the recent debug_backtrace discussion, and the > > discussion about just what we are releasing next and so on, I'd just > > thought I would make a couple of comments about PHP 4

Re: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-21 Thread Sterling Hughes
> Hi all, > > Following on from the recent debug_backtrace discussion, and the > discussion about just what we are releasing next and so on, I'd just > thought I would make a couple of comments about PHP 4.3 and about what > I think (IMHO) should be the goals of PHP 5. > > I'm currently r

RE: [PHP-DEV] PHP 4.3 and PHP 5

2002-08-20 Thread Robinson, Mike
Title: RE: [PHP-DEV] PHP 4.3 and PHP 5 Wez Furlong wrote: > o Bundle Brads php-soap extension, and "market" PHP 5 as > being "Web Service Enabled". This will stop the "bleeding of the PHP users" Manuel Lemos will be pleased. :P Mike Robinso