Quote:
Originally posted by crockett
If I did this I assume you are meaning compiling each page in let's say Zend or something similar.. Would the SE engines still be able to crawl the pages if I did that? That is the most imporant goal is to be SE friendly.
I like the idea of doing the pages in PHP becouse I could make the pages a little more dnymanic that way.
However I know almost nothing about PHP, but I can learn what ever I need to.. I'm just trying to do this right from the start, becouse I'm building these pages mostly by hand so I don't want to redo them anytime soon.
|
A compiler cache is an add-on to PHP.
You don't have to do anything manually except configure the cache once. Basically it interfaces with the Zend engine so that when a script is compiled it saves it and on future requests it uses the pre-copmiled script rather than re-compiling it every time someone requests the document, which is the way it works without the cache (and is why PHP is slower than using a compiled language like C).
Another thing you can do.. if you want to be as SE-friendly as possible and have the benefit of a compiler cache without actually having to install and configure one is what I do on my TGPs..
I run php on the command line to generate static pages. So for example..
$ php -q main.php > index.html
You can set that up with cron so that it runs once per day, or every 5 minutes or whatever you need to keep your site updating when it's supposed to. With this you have pretty much all the benefits of a compiler cache (the script is compiled more often than it would be with a cache but surfers get a static page which is faster than PHP no matter what - even with a cache) and you illiminate any SE un-friendliness that PHP might introduce.