Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63233
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 64.22.89.133 as permitted sender)
Message-ID: <5060A263.8080906@ajf.me>
Date: Mon, 24 Sep 2012 19:11:47 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: ivan.enderlin@hoa-project.net
CC: internals@lists.php.net
References: <505C4A06.6040304@hoa-project.net> <5060A1C5.8070701@ajf.me>
In-Reply-To: <5060A1C5.8070701@ajf.me>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] POST, content-type: application/json and json_decode
From: ajf@ajf.me (Andrew Faulds)

On 24/09/12 19:09, Andrew Faulds wrote:
> I think perhaps that's the wrong approach. It's valid JSON to have a 
> list literal at the top level as well,
Excuse my brief brain lapse. PHP arrays are fine for sequential data as 
well, and you could also have any other JSON literal value in $_POST.

(Although, decoding objects to arrays would be inconvenient, I'd much 
prefer to decode to objects, and doing that might be confusing 
considering $_POST is usually an associative array...)

-- 
Andrew Faulds
http://ajf.me/