Re: serialize and cache handling
| From: | Derick Rethans | Date: | Tue, 08 May 2007 06:17:28 +0000 |
| Subject: | Re: serialize and cache handling | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-29303@lists.php.net to get a copy of this message | ||
On Mon, 7 May 2007, Lukas Kahwe Smith wrote:
> Stanislav Malyshev wrote:
> > > can write this data to disk. So, you needs 20MB. If serialize (and of
> > > course unserialize) would be able to write directly to disk (or read
> > > directly from disk), you only needs 10MB.
> >
> > Actually having serialize/unserialize be able to write directly to a stream
> > and read directly from a stream might be interesting, would probably improve
> > working with things like large sessions or caching large data substantially.
>
> Indeed, especially since this is the most common use case. Maybe it should
> optionally also return an md5 of the written data.
If we're to add this, make sure writes to the files are atomic.
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org