Intended Audience Introduction The Caching Imperative The Script Caching Solution The Caching Script Implementation: Avoiding Common Pitfalls Summary The Script About the Author Intended Audience This article is intended for the PHP programmer interested in creating a static HTML cache of dynamic PHP scripts. The article has been written specifically for an Apache server running PHP scripts, but the ideas described here are applicable to almost any Web environment. The article assumes that you have some experience with creating dynamic Web sites and that you are familiar with HTTP – at least enough to know what a "404 Page Not Found" error means and the definition of the environment variables $REQUEST_URI and $DOCUMENT_ROOT. Introduction The benefits to using dynamic Web pages are well known, but there are nonetheless two significant drawbacks: speed and search engine accessibility. Speed: The speed in which a user receives a page after clicking a link or entering a URL is a crucial factor for a Website. It depends on dozens of variables, some of which you may have control over and some of which you don’t. There are countless bottlenecks in the process, and it’s probably impossible to fix them all. This bottleneck we will tackle here is the one caused by waiting for the server side scripts to create the HTML output. Search Engine Accessibility: By this I mean the ability of search engines to point to a particular Web page. Most search engines function by using a "Crawler" program. Crawler programs begin on a certain page and navigate through the links on it. Every page a crawler visits is then indexed on the search engine’s database. Most crawlers, however, are only programmed to navigate through static (HTML) pages – not dynamic ones. So, for example, pages with URLs that contain a "?" character (indicating a query string) or a filename ending with ".php" will not be accessed. Consequently, crawlers will not index these pages, making your site less accessible to new visitors. Note: A crawler cannot tell the difference between an HTML file’s output and a PHP file’s. They both send the same content type. Therefore, most crawlers simply decide according to the filename and/or if there is a query string in the URL – that is, if the URL contains a "?". This article discusses a procedure for dealing with both of these drawbacks. The article’s script should be sufficient for use under most circumstances – but in particular, small scale Web sites and individual script pages that are only moderately subject to change (dynamics). The Caching Imperative Simply speaking, caching entails storing the output of one or more dynamic scripts into static HTML files. A visitor to your site would be directed to these HTML files rather than to their original dynamic versions. The mechanism for doing so can be described using a Magazine’s Web site as an example. A Magazine’s Web site would likely have a database that contained numerous articles and stories. You would normally have a script (say "show_article.php") that: Receives an article ID number Reads the article’s content from the database Puts it into some kind of HTML template Formats the whole page with navigation links etc... Sends the resulting HTML to the visitor’s browser As such, in the site’s homepage you might have links to current articles coded as follows: Cache Article Now, articles tend to be static and you would hope that the site was operating under heavy request loads (because it’s popular!!). Consequently, requests for each article would undergo extensive processing – meaning access database, search article, and display it. Moreover, when you depend on other database information such as layout specifications, then the process would take even longer. Lastly, a search engine’s crawler would not even index the content of your article(s) because the link to the article page contains a "?" and a ".php" extension, and thus the crawler would not follow it. Therefore, to alleviate these problems a Webmaster should at least consider implementing some form of caching system. When You Should Cache a Script While the caching solution presented in this article will be beneficial to many users, there will be circumstances when you will prefer not to cache your scripts at all or use a different caching method. Scripts that must deal with frequently changing data such as stock values, discussion forums or process forms are not fit for the system described in this article. Under these cases, the decision is up to you – you might decide to leave them dynamic or you might opt for a more advanced solution such as using the Zend Cache. Note: Using the Zend Cache for your site caching needs would render the system described in this article totally unnecessary (though you might still want to read it in order to improve your PHP skills !). The Zend Cache provides you with a complete turnkey caching solution. For a complex site I would advise buying it (and I’m not just saying this because this is Zend’s site but because the application is both easier to maintain and is well supported. On the other hand, if your site only features a few basic scripts, then you probably do not need to bother with caching at all. Nonetheless, if you: Feature (at least relatively) complex scripts on your site, Wish to be able to handle numerous page hits, and/or Cannot afford the cost of a commercial caching solution, then I hope this caching mechanism will serve you well. For pages that do not need to be kept up to the minute, the speed of this system cannot be beaten since it creates pure static HTML pages. The Script Caching Solution The standard caching system solution is to generate static HTML files. From the earlier example, then, the link to the cache article will now be coded as follows: Cache Article id_123.html contains the output generated by the show_article.php script when it is called using id=123. It is a good practice to store all of the cached files under a single directory of their own (in the above example, it was the "/cache" directory) with sub-directories named for each creating dynamic script (i.e. "show_article/" directory). In this manner, the cached files are separated from the dynamic scripts, making site maintenance that much easier to manage – for example, you can easily perform actions such as deleting old cached files generated by a certain script. More importantly, however, it simplifies cache.php’s string replacement mechanism. For more details, refer to cache.php details. Be aware that links to your dynamic pages will need to be switched to point to their respective HTML scripts (output). So, if you would want article #123 to be cached, for example, you would simply change the link from DownloadFilesa2004-11-01"show_article.php$id=123" to "cache/show_article/id_123.html". Note: The HTML files do not have to be defined before assigning these new links. A script is not cached until it has been called by the Server. Furthermore, since the HTML files will reside under a different URL, any relative paths from within those files (e.g. "http://www.myserver.com/path/to/images/art.gif") will need to be corrected. Therefore, consider working with absolute paths such as "http://www.myserver.com/path/to/images/art.gif" or "/path/to/images/art.gif" – note the preceding "/" , meaning relative to the current server . Alternatively, you can add a
tag to your HTML section. Note: It is NOT recommended that you change the paths to relative paths from the cache directory (such as "../../path/to/images/art.gif"
http://www.bkjia.com/PHPjc/531744.htmlwww.bkjia.comtruehttp://www.bkjia.com/PHPjc/531744.htmlTechArticleIntended Audience Introduction The Caching Imperative The Script Caching Solution The Caching Script Implementation: Avoiding Common Pitfalls Summary The Script About the Author In...
