Re: Re: [ANNOUNCEMENT] Cache-1.5.4 (stable) Released.
| From: | Alan Knowles | Date: | Fri, 02 Apr 2004 00:47:24 +0000 |
| Subject: | Re: Re: [ANNOUNCEMENT] Cache-1.5.4 (stable) Released. | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-26949@lists.php.net to get a copy of this message | ||
These look like bugs, rather than deficiencies...
Anyone who knows cache, care to comment...
Deficiencies of Cache_file
* Stores data hex-encoded on disk. Overhead is incurred when saving or retrieving cached data.
* Cache must be used to access the cached data due to the encoding.
* File sizes are increased due to the encoding.
* Userdata with linebreaks can't be stored.
Regards
Alan
Ian Eure wrote:
On Thursday 01 April 2004 08:28 am, Stefan Neufeind wrote:-- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.comHmm - we had a Cache_DB in a stable package which never really worked, as you say? Ugggh ... I'm curious if "trifile" is a good (read: intuitive) name. After leading the webpage, I still don't get what it does so special, and where the name comes from. Is it just me?Trifile's name derives from the fact that it uses three seperate files for storing cache data. The background for why I wrote Trifile, as well as it's advantages over File can be found here: http://atomized.org/PEAR/Cache_trifile.html