Ilia A. wrote: > Caching is not going against PHP as long as whenever the file is changed of > the 1st access it would be cached, rather then caching php scripts based on > some arbitrary timer. > > Ideally the caching script would on the 1st access of the script convert the > script to binary code which can then be executed right away without needing > to pass through an interpreter. Just like you would run a compiled C program. > I suspect such caching solution would greatly boost the speed of any PHP > page. Unfortunately, as far as I know no current PHP caching solution does > this. >
It's not PHP's place to do this. Currently, it would be Zend's place to do this, as they have somewhat of a monopoly on the PHP engine. Obviously not a "monopoly" like, well, MS, but there's not any notable support or demand for alternative PHP engines. Current caches cache the zend 'opcodes' (as far as I can tell), and the Zend engine translates to machine code during execution. If anything was to do this, that's the place where it would/should happen. I'd read about someone planning a PHP -> C compiler, but haven't seen anything on it yet. This might alleviate speed problems for people (although it would introduce a longer write/compile/test cycle). Michael Kimsal http://www.logicreate.com/ 734-480-9961 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
