mod_mem_cache v1.1 for lighttpd released
Published November 22nd, 2006 in TechUpon Jan's kind suggestions, I cleanup mod_mem_cache source to conform lighttpd's coding style. configuration names are changed.
When mem-cache.expire-time=0, mod_mem_cache will compare etag of file with cached-etag, if no difference write cached content. This behaviour is different with previous mod_mem_cache version.
mod_mem_cache has following configuration:
- mem-cache.enable. enable or disable mem_cache, default to enable
- mem-cache.max-memory. maxium memory in Mbytes used by mod_memcache, default is 512(means 512M memory).
- mem-cache.max-file-size. maxium size in kbytes for single cache file, default is 512(means 512k bytes).
- mem-cache.lru-remove-count. number of cached items to remove when used memory reached maxmemory by LRU algorthim. default is 200.
- mem-cache.expire-time. cache's expire time in minutes. default is zero which means to check etag every time
- mem-cache.filetypes. content-type arrays which want to put into cache content. default is not set which means to cache all types. for examples: mem-cache.filetypes=("text/css") to cache css files only.
Changelog:
- configuration names changed
- use buffer as cache content instead void data
what's change in server-statistics? now I saw information about fastcgi not mem_cache anymore.
no change on server-statistics