Re: HEADS UP: Upcoming Feature Freeze for PHP 5.5.0
| From: | Pierre Joye | Date: | Fri, 25 Jan 2013 19:02:45 +0000 |
| Subject: | Re: HEADS UP: Upcoming Feature Freeze for PHP 5.5.0 | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-65188@lists.php.net to get a copy of this message | ||
On Fri, Jan 25, 2013 at 7:48 PM, Zeev Suraski <zeev@zend.com> wrote:
>> -----Original Message-----
>> From: Pierre Joye [mailto:pierre.php@gmail.com]
>> Sent: Friday, January 25, 2013 8:42 PM
>> To: Zeev Suraski
>> Cc: Rasmus Lerdorf; Ralf Lang; PHP internals
>> Subject: Re: [PHP-DEV] HEADS UP: Upcoming Feature Freeze for PHP 5.5.0
>>
>> hi Zeev,
>>
>> On Fri, Jan 25, 2013 at 5:25 PM, Zeev Suraski <zeev@zend.com> wrote:
>> >> Either by a number of people stepping up to help with the existing
>> >> APC
>> > code, or
>> >> perhaps more realistically making it a priority in PHP 5.6 to
>> >> streamline
>> > the
>> >> engine and the executor for opcode caching and either including a
>> > heavily
>> >> simplified version of APC or writing a new one.
>> >>
>> >> One thing I can guarantee is that if we add it to core in its current
>> > condition it
>> >> will delay 5.5 by 6+ months if not longer.
>> >
>> > There's another option. We have the Optimizer+ component which is
>> > current, a bit faster than APC, worked with PHP 5.4 from the get go
>> > and already fully supports 5.5 - and now that it's been free for use
>> > for several years, we'd actually be happy to opensource it and make it
>> > a part of core. An extra benefit would be that we'd commit to
>> > maintain it, although of course, community contribution will be very
> welcome.
>> > Here too, it's code with a very long history, some of which even
>> > predates PHP 4.0. But It Works(tm), and we could put some effort into
>> > cleaning it up and beautifying it.
>>
>> Thanks, That sounds great.
>>
>> > I think we can actually do it on time for 5.5.0, or with a relatively
>> > minor delay that might be worth it. I'm sure most users would prefer
>> > the version to take a bit longer if it comes with an opcode cache
>> > right off the bat.
>> > There'll most probably be APIs we'd want to merge from APC, but doing
>> > that should be easy - and we can get the good of both worlds.
>>
>> Please don't bring over the user cache, please don't :-)
>
> Sounds like there's concensus we don't want these things coupled, so we
> should probably handle that part separately :)
>
>>
>> Quesiton: Does it support both NTS and TS?
>
> I think it used to but if it did that part hasn't been maintained for a
> very long time. Not sure where it stands right now...
That's where APC is very stable, we have spent quite some time to make
it TS-ready, windows and linux. That's an area where I can help.
Cheers,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org