File cache class 2008.02.03 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News File cache class 2008.02.03 (Default branch)
# 1  
Old 02-04-2008
File cache class 2008.02.03 (Default branch)

File cache class is a PHP Class that can cache arbitrary data in files in order to reduce the time necessary to regenerate pages or other types of data that do not change every time they are requested. It features safe locking of cache files to avoid data corruption caused by simultaneous accesses during cache file updates, portable locking schemes, and the ability to set a cache expiry date or timeout period. Cache files can store user-defined headers besides the cached data, and also standard headers used in HTTP like content-length:, date:, expires:, etag:, etc. It has been tested under Linux, SunOS and Windows. License: Freely Distributable Changes:
This release fixes a bug that was preventing the reading of cache file headers longer than the default file buffering length limit.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
libcache(3)						   BSD Library Functions Manual 					       libcache(3)

NAME
libcache -- the caching framework SYNOPSIS
#include <cache.h> DESCRIPTION
The libcache framework provides a facility for creating in memory data caches. Each cache is a mutable dictionary that associates values with their keys. A cache limits the number of values it keeps according to available system memory and selects values to evict when the limit is exceeded. Recently and frequently used values are less likely to be selected for eviction. Cache keys and values should be cast as pointers. The framework provides a callback interface for supporting arbitrary types of keys and values and implements callback functions for common types. See cache_callbacks(3) for more information. Clients retrieve a value previously added to a cache using the value's key. When the client gets a value, the cache increments a reference count on the value. When the client finishes with a value retrieved from a cache they must release the value back to the cache. Referenced values are considered in use and will not be evicted. The cache may evict unreferenced values (e.g. to make room for other values or reduce its size). The number of values allowed in a cache at one time is managed by the cache framework. Cache size will grow when the system has available memory and shrink under memory pressure. Libcache is thread-safe. It is not safe to call back into the cache API from cache callback functions. SEE ALSO
cache_create(3), cache_set_and_retain(3) Darwin May 7, 2009 Darwin