On Tue, Jan 29, 2013 at 11:26 AM, Florin Razvan Patan <florinpa...@gmail.com > wrote:
> Thank you for this great initiative! > > As a user, I could definitely wait for 2-3 more months and get > a good implementation/integration of this rather that have to > wait for at least one year. > > I think it would also be nice if this could come as default > enabled since this way people would be able to notice the > advantages of having it enabled. Or you can run a survey on > php.net to see what are the options. > > I do have one thing to ask you about this. > > If we do wait 2 months, will the underlaying changes be able > to integrate easy with APC/XCache/eAccelerator/others? > > Opcodes are a must for large traffic websites like those I'm > working on right now, so we clearly want to have such a thing > installed on our servers as soon as we install a new PHP > version. But if including O+ will mean that APC gets delayed > 6+ months (see PHP 5.4) it would be a show stopper for us > upgrading to PHP 5.5. > > Our upgrade process is like this: be at least one year on market > to iron out major/obvious bugs. If APC gets on the market 6 > months after PHP 5.5 only because of this then we'll be near > PHP 5.6 by then. And we can't just change from APC to others > as we'll need to test them as well as see which other use data > caching like APC has. > > It would make sense to actually see how the whole ZE can > be improved so that it makes life of opcode cachers easier > and then ship O+ bundled with a PHP version that has better > support for them out of the box if I were to choose. > > > please don't top on this list, we prefer bottom or inline posting around here, see http://www.php.net/reST/README.MAILINGLIST_RULES back to the topic: personally I think that even two months seems like a tight schedule as we are talking about incorporating an opcode cache, which I'm pretty sure that it is similar in complexity to apc, and are only like a handful of people on the planet has any experience working with, and needs some polishing and has at least one known shortcoming (thread safety). my opinion is that we should wait for the code to be released before thinking about the release dates. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
