Output Caching with PHP - Output Buffering for Server Side Caching
(Page 3 of 5 )
Now, with this example in our hands, let’s see how we can use output buffering for server side caching. Let's implement a very simple demonstration, where the buffer content is stored as a file:
<?php
// check if there is a cached version
if ( file_exists( ‘cachefile.txt’ ) ) {
// if there is a cached version read content and display
readfile ( ‘cachefile.txt’ );
exit();
}
// if there is not a cached version start output buffering
ob_start();
// display some HTML ( this will be stored in the buffer )
?>
<html>
<head>
<title>Caching server output</title>
</head>
<body>
<h2>This page is a cached Page</h2>
</body>
</html>
<?php
$bufferContent = ob_get_contents();
// get buffer content
ob_end_flush();
// clean and display buffer content in the browser
$fp = fopen ( ‘cachefile.txt’ , ‘w’ ) or die ( ‘Error opening cache file’ );
// write buffer content to cache file
fwrite ( $fp , $bufferContent );
fclose( $fp );
?>
The output for the above script is the parsed HTML:
This page is a cached Page
The contents of the cache file ‘cachefile.txt’ is the same HTML included in the script:
<html>
<head>
<title>Caching server output</title>
</head>
<body>
<h2>This page is a cached Page</h2>
</body>
</html>
Let’s examine in detail what’s going on within the script:
First, the script checks to see if there is a cached version of the page, by determining if a cache file exists. If it does, it then reads the cache file and send the output to the browser. Otherwise, it starts a new output buffer and store some HTML on it to generate the cached version. Once this is done, it gets the buffer content and stores it in a variable ($bufferContent). Next, the buffer is cleared and the HTML is displayed to the user. Finally, the buffer content is written to the cache file.
Obviously, this script is very simple, but exposes in a nutshell the powerful caching capabilities that PHP has built-in, when used in conjunction with output buffering functions. Having all of this potential in our hands, the logical next step is caching different sections of a Web page. Web pages usually have a header section, body and a footer section. It would be good to apply these caching techniques accordingly to how frequently those generic sections are updated. We’re moving that way now.
Next: Multiple caching: splitting the Web page content >>
More PHP Articles
More By Alejandro Gervasio
|
| · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | | |
|
