Re: APC & Custom streams

Greg Beaver wrote:

Roger. Anyway, the "gain" of including wrapped streams is probably small compared to the cost of issuing url_stat()s, just wanted to be clear. One thing this does mean though is that the payload portion of PHARs won't be cached.

Because of this, PHP_Archive implements a run-time memory-based cache.

But doesn't run-time mean "new cache for every request"? And if you use mod_php, don't you use one cache for each Apache process?

It would be really easy to simulate the inode/mtime stuff in PHP_Archive if APC was modified to use the wrapper code, incidentally.

I think people using APC, don't really need PHAR. If you can install APC, you also can use the pear installer to install packages with PHP files. I'm not sure, but is it possible to cache the same opcodes from a PHAR, as if you would cache the PHP files contained in the PHAR file? And will checking inode/mtime for changes be as fast as for files using stat? Or what about implementing something for PHARs to make it possible to create local PHP files from the archive? I think opcode caches like APC have been designed to cache the opcodes generated from local PHP files. If someone wants to distribute PHP files why not using a tool designed for something like that, e.g. rsync? And perhaps using the wapper code will slow down APC? best regards Andreas