blob: 0e2cfe37083bc8b66acbd630a01ca674eab4c963 [file] [log] [blame]
<?php
/**
* File containing the ezcCacheStorageArray class.
*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*
* @package Cache
* @version //autogentag//
* @license http://www.apache.org/licenses/LICENSE-2.0 Apache License, Version 2.0
* @filesource
*/
/**
* This cache storage implementation stores arrays and scalar values
* (int, float, string, bool) in files on your hard disk as PHP code. This makes
* the restoring of cache data extremly fast, since the stored data is simply
* included and parsed by the PHP interpreter. It takes its base methods from
* the extended storage base class {@link ezcCacheStorageFile}.
*
* Another storage class with a similar approach exists,
* {@link ezcCacheStorageFileEvalArray}. This class is uses exactly the same
* mechanisms as ezcCacheStorageFileArray, except that is does not simply
* require the stored source code, but uses eval() to restore the data.
*
* Main purpose behind these 2 similar implementations is the following:
* Most byte code caches are capable of caching code for included files,
* but not for eval()ed strings. Therefore the *Evalarray class will
* permit you to get your cached data not cached a second time by an
* accellerator like APC, whereas the *Array class will permit you to
* explicitly allow this. ATTENTION: If you do not use a byte code cache
* with your PHP installation, the use of ezcCacheStorageFileArray is
* recommende over the usage of ezcCacheStorageEvalarray.
*
* For example code of using a cache storage, see {@link ezcCacheManager}.
*
* The Cache package contains several other implementations of
* {@link ezcCacheStorageFile}. As there are:
*
* - ezcCacheStorageFileEvalArray
* - ezcCacheStorageFilePlain
*
* @package Cache
* @version //autogentag//
*/
class ezcCacheStorageFileArray extends ezcCacheStorageFile
{
/**
* Fetch data from the cache.
* This method does the fetching of the data itself. In this case, the
* method simply includes the file and returns the value returned by the
* include (or false on failure).
*
* @param string $filename The file to fetch data from.
* @return mixed The fetched data or false on failure.
*/
protected function fetchData( $filename )
{
return ( include $filename );
}
/**
* Serialize the data for storing.
* Serializes a PHP variable (except type resource and object) to a
* executable PHP code representation string.
*
* @param mixed $data Simple type or array
* @return string The serialized data
*
* @throws ezcCacheInvalidDataException
* If the data submitted is an object or a resource, since this
* implementation of {@link ezcCacheStorageFile} can only deal with
* scalar and array values.
*/
protected function prepareData( $data )
{
if ( is_object( $data ) || is_resource( $data ) )
{
throw new ezcCacheInvalidDataException( gettype( $data ), array( 'simple', 'array' ) );
}
return "<?php\nreturn " . var_export( $data, true ) . ";\n?>\n";
}
}
?>