Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42230 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85124 invoked from network); 13 Dec 2008 03:58:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Dec 2008 03:58:52 -0000 Authentication-Results: pb1.pair.com header.from=mike503@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=mike503@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.227 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: mike503@gmail.com X-Host-Fingerprint: 209.85.198.227 rv-out-0506.google.com Received: from [209.85.198.227] ([209.85.198.227:27754] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7A/91-16788-BF233494 for ; Fri, 12 Dec 2008 22:58:52 -0500 Received: by rv-out-0506.google.com with SMTP id g37so1828752rvb.23 for ; Fri, 12 Dec 2008 19:58:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=XUcfzE1RQ9mwN9ftqe86MMlv1aGauIeUuQbblDwzgms=; b=BvvJq4R/94YG/q3nM3yIjiYsBQhm4lJHEiiOj3wqjPzQC9vE3S+iKJcGwG4s6X53Ym acmU86m/nAavncBLCNNq4ez3+w2GER0SdKFru3c72Guf2TVFERPFFNDDAiEoZ4cFNXQ1 /JSipOBf9mHBKz9vVAMpkkuqjZYm7kFJHwSbc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=qgmkT+H/8NmfmTRqLE2aJhkt2vc5UTFhgx1/800cTILsjZflEpgyqGy5AinVSBY5go 45WxZOSSRj//JGKFYj9e69LgYsLQA6ltbGexMje2LRQWzjY1Iibh4j8F5sTJ1JbaQggx NglRqB7HZ7pjq+UwXGFedNYXbI5xbOAOB0lJU= Received: by 10.140.201.8 with SMTP id y8mr2294312rvf.101.1229140728346; Fri, 12 Dec 2008 19:58:48 -0800 (PST) Received: by 10.141.146.16 with HTTP; Fri, 12 Dec 2008 19:58:48 -0800 (PST) Message-ID: Date: Fri, 12 Dec 2008 19:58:48 -0800 To: "Scott MacVicar" Cc: "PHP Developers Mailing List" In-Reply-To: <2D85B33E-889B-4214-9BB8-A12EFFFC641E@macvicar.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2D85B33E-889B-4214-9BB8-A12EFFFC641E@macvicar.net> Subject: Re: [PHP-DEV] Removing basic types from our JSON parser From: mike503@gmail.com (mike) Fri, Dec 12, 2008 at 7:50 PM, Scott MacVicar wrote: > The problem here is that none of the other JSON parsers in any other > language support this and more importantly the browsers [2] which are now > adding native JSON support. Users are frequently expecting the result from a > json_encode in PHP to just work with JSON.parse() on the client side. [3] > > I have a patch for this that implements the RFC exactly and makes secure > json_encode only works with objects and arrays. definately +1 we use json both encoding and decoding to interact with javascript and ensuring that PHP's built-in json is standards compliant is an absolute must. -please- make sure it works both encoding php -> js, decoding js -> php for all relevant types in both languages. thank you :)