Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65537
Return-Path: <glopes@nebm.ist.utl.pt>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 17537 invoked from network); 31 Jan 2013 11:19:09 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 31 Jan 2013 11:19:09 -0000
Authentication-Results: pb1.pair.com smtp.mail=glopes@nebm.ist.utl.pt; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=glopes@nebm.ist.utl.pt; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.21 cause and error)
X-PHP-List-Original-Sender: glopes@nebm.ist.utl.pt
X-Host-Fingerprint: 193.136.128.21 smtp1.ist.utl.pt Linux 2.6
Received: from [193.136.128.21] ([193.136.128.21:60440] helo=smtp1.ist.utl.pt)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 0C/D3-09318-A235A015 for <internals@lists.php.net>; Thu, 31 Jan 2013 06:19:07 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp1.ist.utl.pt (Postfix) with ESMTP id 64A147000450;
	Thu, 31 Jan 2013 11:19:03 +0000 (WET)
X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at ist.utl.pt
Received: from smtp1.ist.utl.pt ([127.0.0.1])
	by localhost (smtp1.ist.utl.pt [127.0.0.1]) (amavisd-new, port 10025)
	with LMTP id SZNngQvPYzDC; Thu, 31 Jan 2013 11:19:03 +0000 (WET)
Received: from mail2.ist.utl.pt (mail.ist.utl.pt [IPv6:2001:690:2100:1::8])
	by smtp1.ist.utl.pt (Postfix) with ESMTP id 193907000424;
	Thu, 31 Jan 2013 11:19:02 +0000 (WET)
Received: from damnation.nl.lo.geleia.net (unknown [IPv6:2001:470:94a2:4:21d:baff:feee:cc0b])
	(Authenticated sender: ist155741)
	by mail2.ist.utl.pt (Postfix) with ESMTPSA id 165FC2008826;
	Thu, 31 Jan 2013 11:19:01 +0000 (WET)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: "PHP Internals" <internals@lists.php.net>, "Ivan Enderlin @ Hoa"
 <ivan.enderlin@hoa-project.net>
References: <510A3B71.7060508@hoa-project.net>
Date: Thu, 31 Jan 2013 12:18:58 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: Quoted-Printable
Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?=
 =?utf-8?Q?ca_do_I=2ES=2ET=2E?=
Message-ID: <op.wrrv9imaidpuyk@damnation.nl.lo.geleia.net>
In-Reply-To: <510A3B71.7060508@hoa-project.net>
User-Agent: Opera Mail/12.12 (Linux)
Subject: Re: [PHP-DEV] Proposal: php://memory/<id> (& ://temp/<id>)
From: glopes@nebm.ist.utl.pt ("Gustavo Lopes")

On Thu, 31 Jan 2013 10:37:53 +0100, Ivan Enderlin @ Hoa  =

<ivan.enderlin@hoa-project.net> wrote:

> The php://memory, and its respectful sibling php://temp, appear very
> useful when we need to compute streams on-the-fly. They offer a lot of=

> services, like avoiding HDD accesses, increasing speed... and through =
a
> straightforward API /=C3=A0 la/ PHP, e.g. fopen('php://memory', 'r+').=

> However, we always work on the same "bucket"/space of data (per
> runtime), which prevent us to use two different streams at a time. My
> proposal is to allow access to many "buckets"/spaces to php://memory a=
nd
> its sibling.
>

I'm not sure what you mean here. Each time you open a php://memory strea=
m,  =

you're working on a new "bucket", right?

$ cat a.php && php a.php
<?php
$f1 =3D fopen("php://memory", "r+");
$f2 =3D fopen("php://memory", "r+");
fwrite($f1, "foobar");

array_map(function($f) {
	rewind($f);
	var_dump(stream_get_contents($f));
}, [$f1, $f2]);
string(6) "foobar"
string(0) ""


-- =

Gustavo Lopes