Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29299 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18436 invoked by uid 1010); 7 May 2007 22:24:13 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 18421 invoked from network); 7 May 2007 22:24:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 May 2007 22:24:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 212.112.227.169 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.5 (sometimes 2.4) (4) Received: from [212.112.227.169] ([212.112.227.169:45245] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 78/99-40634-B07AF364 for ; Mon, 07 May 2007 18:24:12 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id AD4A9DF0123; Tue, 8 May 2007 00:24:08 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (flottensignalgeber [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12010-02; Tue, 8 May 2007 00:24:06 +0200 (CEST) Received: from [127.0.0.1] (dt0f2n29.tampabay.res.rr.com [24.92.178.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ipx11223.ipxserver.de (Postfix) with ESMTP id E5456DF0085; Tue, 8 May 2007 00:24:04 +0200 (CEST) Message-ID: <463FA701.5030707@pooteeweet.org> Date: Mon, 07 May 2007 18:24:01 -0400 User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Stanislav Malyshev Cc: Mathias Bank , internals@lists.php.net References: <0E.B4.18102.F9DB9264@pb1.pair.com> <463F9FD0.3030009@zend.com> In-Reply-To: <463F9FD0.3030009@zend.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] serialize and cache handling From: mls@pooteeweet.org (Lukas Kahwe Smith) 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. regards, Lukas