[PHP-DEV] phar concerns? (was Re: [PHP-CVS] cvs: php-src /ext/bz2 bz2_filter.c)

2009-02-14 Thread Greg Beaver
Hannes Magnusson wrote: > I still find Phar way to dangerous to _enable by default_ and I > still do not think you are *fit* to handle such extension. (Yes, I did > indeed say it. And I will not apologize for it. I really don't.) > ok. :] > You have your own agenda (just like everyone else),

[PHP-DEV] Re: [PHP-CVS] cvs: php-src /ext/bz2 bz2_filter.c

2009-02-14 Thread Hannes Magnusson
(private, feel free to take online if you want to) On Sun, Feb 15, 2009 at 05:00, Greg Beaver wrote: > Hannes Magnusson wrote: >> On Sat, Feb 14, 2009 at 16:25, Greg Beaver wrote: >> >>> Hannes Magnusson wrote: >>> On Thu, Feb 5, 2009 at 22:32, Greg Beaver wrote: > I really d

[PHP-DEV] Re: [PHP-CVS] cvs: php-src /ext/bz2 bz2_filter.c

2009-02-14 Thread Greg Beaver
Hannes Magnusson wrote: > On Sat, Feb 14, 2009 at 16:25, Greg Beaver wrote: > >> Hannes Magnusson wrote: >> >>> On Thu, Feb 5, 2009 at 22:32, Greg Beaver wrote: >>> >>> I really don't give a crap. Change it if you want, I was merging *existing* code in PHP_5_3 to HEAD, n

RE: [PHP-DEV] 5.3 todos

2009-02-14 Thread Andi Gutmans
> -Original Message- > From: Hannes Magnusson [mailto:hannes.magnus...@gmail.com] > Sent: Saturday, February 14, 2009 6:04 PM > To: Andi Gutmans > Cc: shire; Lukas Kahwe Smith; PHP Internals List > Subject: Re: [PHP-DEV] 5.3 todos > > And you are? > CTO of some company? Claiming you wrote

Re: [PHP-DEV] 5.3 todos

2009-02-14 Thread Hannes Magnusson
On Sun, Feb 15, 2009 at 00:08, Andi Gutmans wrote: >> -Original Message- >> From: shire [mailto:sh...@tekrat.com] >> Sent: Thursday, February 12, 2009 11:02 AM >> To: Lukas Kahwe Smith >> Cc: PHP Internals List >> Subject: Re: [PHP-DEV] 5.3 todos >> >> >> Seeing as I have an interest in th

[PHP-DEV] Re: [PHP-CVS] cvs: php-src /ext/bz2 bz2_filter.c

2009-02-14 Thread Hannes Magnusson
On Sat, Feb 14, 2009 at 16:25, Greg Beaver wrote: > Hannes Magnusson wrote: >> On Thu, Feb 5, 2009 at 22:32, Greg Beaver wrote: >> >>> I really don't give a crap. Change it if you want, I was merging >>> *existing* code in PHP_5_3 to HEAD, not adding new stuff. >>> >> >> Which is exactly why we

RE: [PHP-DEV] 5.3 todos

2009-02-14 Thread Andi Gutmans
> -Original Message- > From: shire [mailto:sh...@tekrat.com] > Sent: Thursday, February 12, 2009 11:02 AM > To: Lukas Kahwe Smith > Cc: PHP Internals List > Subject: Re: [PHP-DEV] 5.3 todos > > > Seeing as I have an interest in this getting in 5_3, I'll work up a patch for > this unless s

[PHP-DEV] [RFC] Better benchmarks for PHP

2009-02-14 Thread Nuno Lopes
Hi, Currently PHP's benchmarks are very poor. The PHP interpreter is only timed against bench.php. Sadly, this doesn't make use of the majority of PHP's features, principally OO, but also includes and variable-variables. We'd like to help rectify that, and have created an RFC with some initial

Re: [PHP-DEV] open_basedir performance issue, realpathcache vs. statcache

2009-02-14 Thread Rasmus Lerdorf
Roland Mieslinger wrote: > Hello, > > we're managing a shared hosting environment with about 600 virtual > servers. All content for the websites is stored on a NFS share. > > We're suffering from a huge amount of lstat calls, and identified > open_basedir as the reason for that. strace shows tha

[PHP-DEV] open_basedir performance issue, realpathcache vs. statcache

2009-02-14 Thread Roland Mieslinger
Hello, we're managing a shared hosting environment with about 600 virtual servers. All content for the websites is stored on a NFS share. We're suffering from a huge amount of lstat calls, and identified open_basedir as the reason for that. strace shows that each call needs 40µs in average, this

Re: [PHP-DEV] Re: Bug #46701

2009-02-14 Thread Moriyoshi Koizumi
Please don't even think of backporting. This will definitely break a lot of things, and this kind of thing must not be done in a minor release. Moriyoshi On Fri, Feb 13, 2009 at 10:57 PM, Ilia Alshanetsky wrote: > Dmitry, > > Does it make sense to backport 42868 fix to address this issue? > > >