On 01/04/2012 11:33 PM, Stas Malyshev wrote: > Hi! > >> Yes, but we still need an actual case to look at. Opcode caches >> shouldn't be a problem unless they store some representation on disk >> that live across server restarts. In the APC world, nobody does that. Is > > It's not that simple. Take example of FastCGI setup where processes can > live and die independently (note that FastCGI does not mandate > single-parent fork and in fact on Windows it doesn't work that way). In > this setup opcode cache is shared between processes which may have > different hash value, unless we give means to the cache to set this > value on startup somehow.
hrm, ok, yes for non single parent forks it is an issue. For APC there is no such thing, although people have been asking for it. With a clean API this doesn't sound insurmountable though. get_hash_seed()/set_hash_seed() internal functions. When the cache is created the first time call get_hash_seed() and store it somewhere. When someone connects to an existing cache the first time, fetch the stored hash seed and call set_hash_seed() -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
