Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48825
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain cdatazone.org does not designate 207.58.142.213 as permitted sender)
Message-ID: <4C1B74C7.2020209@cdatazone.org>
Date: Fri, 18 Jun 2010 09:29:43 -0400
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Hans-Peter Oeri <hp@oeri.ch>
CC: internals@lists.php.net
References: <7E.F9.36621.35A2A1C4@pb1.pair.com>
In-Reply-To: <7E.F9.36621.35A2A1C4@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject:  Re: [PHP-DEV] Why not attach XMLReader / XMLWriter to open php streams?
From: rrichards@cdatazone.org (Rob Richards)

Hans-Peter Oeri wrote:
> Hi!
>
> As documented - and several searches did not lead to a different result
> - XMLReader and XMLWriter can only work on an URI. That would be a php
> stream opened and closed by themselves.
>
> For several workflows, e.g. with php://temp, it would be nice to be able
> to "attach" XMLReader/XMLWriter to a pre-opened php stream. I would
> describe it as letting them work "on a stream" instead of "on an uri".
>
> As I didn't find anything about it: Is there a reason for not supporting
> 'stream resources'? Other extension, like e.g. curl, do.
>
> HPO
>
>   

There never was a real need for this. Can easily be done by creating 
your own stream wrapper and feeding the already opened streamed through it.

Rob