Re: Re: [ANNOUNCEMENT] Cache-1.5.4 (stable) Released.
| From: | Ian Eure | Date: | Sat, 03 Apr 2004 19:43:22 +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-27004@lists.php.net to get a copy of this message | ||
On Saturday 03 April 2004 03:19 am, Stefan Neufeind wrote:
> On 1 Apr 2004 at 17:05, Ian Eure wrote:
> > On Thursday 01 April 2004 04:47 pm, Alan Knowles wrote:
> > > 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.
> >
> > Userdata with linebreaks is definitely a deficiency, but I don't believe
> > that the other items are bugs.
>
> But why can't a binary file be stored as such? Imho it is much
> overhead to convert e.g. a image or large zip-archive to hex and back
> again.
>
Now it can, with Cache_trifile, which does store the data (not necessarily a
file) in raw format on-disk. Cache_file may have other perfectly acceptable
uses.