Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43932 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15166 invoked from network); 14 May 2009 16:58:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2009 16:58:05 -0000 Authentication-Results: pb1.pair.com header.from=andrei@gravitonic.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=andrei@gravitonic.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain gravitonic.com from 209.85.216.125 cause and error) X-PHP-List-Original-Sender: andrei@gravitonic.com X-Host-Fingerprint: 209.85.216.125 mail-px0-f125.google.com Received: from [209.85.216.125] ([209.85.216.125:53979] helo=mail-px0-f125.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/95-27038-C9D4C0A4 for ; Thu, 14 May 2009 12:58:05 -0400 Received: by pxi31 with SMTP id 31so636669pxi.29 for ; Thu, 14 May 2009 09:58:01 -0700 (PDT) Received: by 10.142.51.4 with SMTP id y4mr768178wfy.131.1242320281791; Thu, 14 May 2009 09:58:01 -0700 (PDT) Received: from barley.local (64-71-7-198.static.wiline.com [64.71.7.198]) by mx.google.com with ESMTPS id 32sm415677wfa.33.2009.05.14.09.57.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 14 May 2009 09:58:00 -0700 (PDT) Message-ID: <4A0C4D97.3090307@gravitonic.com> Date: Thu, 14 May 2009 09:57:59 -0700 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: PHP internals Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Request decoding in PHP 6 [patch] From: andrei@gravitonic.com (Andrei Zmievski) Request decoding is one of a few remaining pieces of the Unicode puzzle. The proposed solution was outlined in a blog post [1] I wrote a while back. There has been no movement on this front pretty much since then, but now that 5.3 is wrapping up I want to put some momentum behind PHP 6. Towards that, I have been working on a patch that implements the request decoding functionality. The patch [2] and the notes [3] are linked to below. This is not a final effort by any means, but I believe the patch is solid and the rest can be done in a similar manner. Right now, it implements only $_POST, $_GET, $_FILES, and $_REQUEST decoding. Deciding how to handle $_COOKIES is the next step, which is mentioned in the notes. Please take a look and comment. -Andrei [1] http://gravitonic.com/2007/02/php-6-and-request-decoding [2] http://gravitonic.com/dump/request_decoding.patch [3] http://gravitonic.com/dump/request_decoding.txt