>> Competition between opcode caches for php will definitely be reduced by >> adding APC into the core, >> so the market will shrink, of course. > > > i think this is a likely outcome indeed. it might also be phrased in a > more > positive tone in that likely efforts will be joined. for example maybe > zend > will decide to contribute some of their code to APC.
my poor english does not allow me to impress it clearly that my tone is as positive as possible :) > so the key question might be more is there something in APC that makes > it fundamentally the right or wrong approach. Is there any possibility for you or anybody else to run all php standard tests under Apache + php with and without APC to see how many among them are broken with APC? Please don't forget to run tests TWICE under APC because on the first run it does not use the cached opcodes. > furthermore does adding any byte code cache to core also enable new kinds > of optimizations > because its now possible to more tightly integrate with core? I'd think of tightly integrated opcode serializer/deserializer and it's what can be highly optimized after adding into the core. This approach would be much cleaner, indeed. -jv -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
