Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29303 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66420 invoked by uid 1010); 8 May 2007 06:17:41 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 66405 invoked from network); 8 May 2007 06:17:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 May 2007 06:17:41 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain php.net from 82.94.239.5 cause and error) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Received: from [82.94.239.5] ([82.94.239.5:45822] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/65-10930-10610464 for ; Tue, 08 May 2007 02:17:38 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.7/8.12.11) with ESMTP id l486HX52003951; Tue, 8 May 2007 08:17:33 +0200 Date: Tue, 8 May 2007 08:17:28 +0200 (CEST) X-X-Sender: derick@kossu.ez.no To: Lukas Kahwe Smith cc: Stanislav Malyshev , Mathias Bank , internals@lists.php.net In-Reply-To: <463FA701.5030707@pooteeweet.org> Message-ID: References: <0E.B4.18102.F9DB9264@pb1.pair.com> <463F9FD0.3030009@zend.com> <463FA701.5030707@pooteeweet.org> X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl' MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Subject: Re: [PHP-DEV] serialize and cache handling From: derick@php.net (Derick Rethans) 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