Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65541
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.21 cause and error)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: internals@lists.php.net, "Ivan Enderlin @ Hoa"
 <ivan.enderlin@hoa-project.net>
References: <510A3B71.7060508@hoa-project.net>
 <op.wrrv9imaidpuyk@damnation.nl.lo.geleia.net>
 <510A77CE.2020308@hoa-project.net>
Date: Thu, 31 Jan 2013 15:35:14 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
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.wrr5g0kvidpuyk@damnation.nl.lo.geleia.net>
In-Reply-To: <510A77CE.2020308@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 14:55:26 +0100, Ivan Enderlin @ Hoa  
<ivan.enderlin@hoa-project.net> wrote:

>> I'm not sure what you mean here. Each time you open a php://memory  
>> stream, you're working on a new "bucket", right?
> Yes exact. My bad. But my proposal still persist. Identifying  
> php://memory buckets would be nice to retrieve them. For example:
>
>      $f1 = fopen('php://memory/foo', 'r+');
>      fwrite($f1, 'foobar');
>      unset($f1);
>
>      $f1prime = fopen('php://memory/foo', 'r+');
>      rewind($f1);
>      var_dump(stream_get_contents($f1)); // string(6) "foobar"
>
> Is it interesting? In this way, we have a similar behavior than  
> php://fd/<i>, file://, http:// etc.
>

No. When you do unset($f1), you're closing the file and the memory is  
reclaimed. That's how it's supposed to be.

Just pass the stream along. If you really need to use operations on the  
URLs themselves, you can easily write a user wrapper that delegates to  
static php://memory streams kept statically.

-- 
Gustavo Lopes