Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23196 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71554 invoked by uid 1010); 8 May 2006 18:14:53 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 71539 invoked from network); 8 May 2006 18:14:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 May 2006 18:14:52 -0000 X-PHP-List-Original-Sender: antony@zend.com X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:56991] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 71/AF-63885-B9A8F544 for ; Mon, 08 May 2006 14:14:52 -0400 Received: (qmail 3999 invoked from network); 8 May 2006 18:14:43 -0000 Received: from internal.zend.office (HELO ?127.0.0.1?) (10.1.1.1) by internal.zend.office with SMTP; 8 May 2006 18:14:43 -0000 Message-ID: <445F8A98.2080604@zend.com> Date: Mon, 08 May 2006 22:14:48 +0400 User-Agent: Thunderbird 1.5.0.2 (X11/20060420) MIME-Version: 1.0 To: Derick Rethans CC: Rasmus Lerdorf , Ilia Alshanetsky , internals Mailing List References: <6E5468C5-630C-48B8-A501-6FC874651D01@prohost.org> <445D8156.8090701@lerdorf.com> <506DE35B-1925-4DA7-8F9F-F23F7D77EE87@prohost.org> <445E0BEF.1080403@lerdorf.com> <445E17ED.8010003@lerdorf.com> <30AC7F22-70A4-4109-8021-9FBF77D408EE@prohost.org> <445E1E51.3010603@lerdorf.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 5.2 Branched From: antony@zend.com (Antony Dovgal) On 07.05.2006 20:27, Derick Rethans wrote: > On Sun, 7 May 2006, Rasmus Lerdorf wrote: > >> Ilia Alshanetsky wrote: >> > Well that can still work, we can access the data from PG(http_globals) >> > without having to duplicate the data at the onset. >> >> Not if we don't enable the extension which is what we are talking about. > > Well, we should enable it by default with the default filter set to > raw... otherwise folks still don't have the input_get functionality > which is the basic point of this extension to me. For me this is much > more useful then JSON... Agree, we need to enable it by default, otherwise including it in the core doesn't make much sense. -- Wbr, Antony Dovgal