Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15404 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60395 invoked by uid 1010); 12 Mar 2005 18:27:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 60372 invoked from network); 12 Mar 2005 18:27:25 -0000 Received: from unknown (HELO pb1.pair.com) (127.0.0.1) by localhost with SMTP; 12 Mar 2005 18:27:25 -0000 X-Host-Fingerprint: 70.85.46.36 unknown Received: from ([70.85.46.36:35464] helo=prohost.org) by pb1.pair.com (ecelerity HEAD r(5124)) with SMTP id D1/44-31540-B8433324 for ; Sat, 12 Mar 2005 13:27:25 -0500 Received: (qmail 6538 invoked from network); 12 Mar 2005 18:27:20 -0000 Received: from cpe00095beeab35-cm000f9f7d6664.cpe.net.cable.rogers.com (HELO ?192.168.1.101?) (69.196.31.219) by prohost.org with SMTP; 12 Mar 2005 18:27:20 -0000 Message-ID: <42333487.70906@prohost.org> Date: Sat, 12 Mar 2005 13:27:19 -0500 User-Agent: Mozilla Thunderbird 1.0 - [MOOX M3] (Windows/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Schneider CC: Moriyoshi Koizumi , internals@lists.php.net References: <4231F330.6000705@prohost.org> <4e89b426050311134633b22b@mail.gmail.com> <4232163C.1000906@prohost.org> <4232D97B.5020305@cschneid.com> In-Reply-To: <4232D97B.5020305@cschneid.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] HALT Patch From: ilia@prohost.org (Ilia Alshanetsky) > Hmm.. I was wondering if we should go one step further and also provide > a stream to the data. If the most common usage of this construct is > going to be reading the data after __HALT_PHP_PARSER__ then we should > optimize for that case. Something like > > $data = gzdeflate(file_get_contents("php://data")); > ?> > > ... I would suggest keeping such implementation in the user-land code rather then the core. It would be fairly trivial to implement a streams wrapper to do this and it can internally handle various decoding schema like decompression etc... Ilia