Re: serialize and cache handling

On Tue, 8 May 2007, Richard Lynch wrote: > On Tue, May 8, 2007 1:17 am, Derick Rethans wrote: > > 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. > > >s this suggesting that the entire 80M upload has to be done in a > >single operation?... Wrong thread ;-) This is on serialize, not on hashes. regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org