Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65529
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <510A3B71.7060508@hoa-project.net>
References: <510A3B71.7060508@hoa-project.net>
Date: Thu, 31 Jan 2013 11:00:02 +0100
Message-ID: <CANqVvahARTC+GF5O=dgopstAYFSsEqQwA9Ag5qsD6weWOpjvnw@mail.gmail.com>
To: ivan.enderlin@hoa-project.net
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d043d644bbbcf7304d492b045
Subject: Re: [PHP-DEV] Proposal: php://memory/<id> (& ://temp/<id>)
From: attila.bukor@gmail.com (Attila Bukor)

--f46d043d644bbbcf7304d492b045
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Ivan,

I've never actually worked with them, but it seems nice. However, we should
make redirect php://memory and php://temp to php://memory/default and
php://temp/default respectively to avoid break stuff imho.

Cheers,
r1pp3rj4ck


On Thu, Jan 31, 2013 at 10:37 AM, Ivan Enderlin @ Hoa <
ivan.enderlin@hoa-project.net> wrote:

> Hi internals,
>
> 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 /=E0 la/ PHP, e.g. fopen('php://memory', 'r+'). Howev=
er,
> 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 allo=
w
> access to many "buckets"/spaces to php://memory and its sibling.
>
> I propose the following syntax:
>
>     php://memory/<id>
>     php://temp/<id>/maxmemory:<**size>
>
> We append /<id> to the existing syntax. Thus, it would be possible to wor=
k
> on php://memory/foo and php://memory/bar without collisions between them.
> They would represent two distinct "buckets"/spaces.
>
> The implementation does not seem to require a ton of work, and the use
> cases are numerous regarding the services offered by these wrappers.
>
> Thoughts?
> Best regards.
>
> --
> Ivan Enderlin
> Developer of Hoa
> http://hoa-project.net/
>
> PhD. student at DISC/Femto-ST (Vesontio) and INRIA (Cassis)
> http://disc.univ-fcomte.fr/ and http://www.inria.fr/
>
> Member of HTML and WebApps Working Group of W3C
> http://w3.org/
>
>

--f46d043d644bbbcf7304d492b045--