Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21602
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7.0.0.16.2.20060120170223.041fb8d0@zend.com>
Date: Fri, 20 Jan 2006 17:03:56 -0800
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: internals@lists.php.net,omar@rmilk.com
In-Reply-To: <43D1625C.3030001@lerdorf.com>
References: <43D13AAE.1030409@lerdorf.com>
	<7.0.0.16.2.20060120134701.04186f60@zend.com>
	<43D1625C.3030001@lerdorf.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] JSON inclusion in core
From: andi@zend.com (Andi Gutmans)

Yeah, but the main problem with this kind of stuff is when you start 
mapping classes and even references. I think it requires some 
additional pluming to be really useful for writing robust 
JavaScript<-->PHP connectivity so that it's flexible enough for all 
those PHP packages to start using it.
I'm +1 for including JSON but not on the way the API is defined right now.

Andi

At 02:21 PM 1/20/2006, Rasmus Lerdorf wrote:
>It's pretty simple.
>
>   string json_encode(mixed whatever)
>   mixed json_decode(string encoded_whatever)
>
>It's just a serializer.
>
>-Rasmus
>
>Andi Gutmans wrote:
>>Hey,
>>I think having a JSON extension for PHP is a good idea. We have 
>>written our own implementation in PHP for framework but could 
>>definitely benefit from a C extension down the road if it gets widely adopted.
>>My only concern is that this is a very new extension and I haven't 
>>seen any docs yet. So generally speaking I'd be a +1 but I prefer 
>>to be able to first review docs, make sure APIs are reasonable and 
>>the best they can be, and then keep it experimental for a while to 
>>make sure it's stable (which would have probably been the case anyway).
>>Andi
>>At 11:31 AM 1/20/2006, Rasmus Lerdorf wrote:
>>>pecl/json is a rather simple extension with no external deps (it 
>>>bundles the small library it uses).  The JSON format is stable 
>>>with no real possibility of changing basically by definition, and 
>>>I see its use exploding this year.  There is also talk to a JSON 
>>>Request object being added to browsers and if that happens we need 
>>>to support that natively much like we support url-encoded form 
>>>data ending up directly in $_POST.  I could see a $_JSON if 
>>>browsers start sending this.  But, as an initial step how about we 
>>>bundle pecl/json in the next release?
>>>
>>>There is an issue with the fact that it is LGPL'ed.  But perhaps 
>>>we can work with Omar to put at least the extension part under the 
>>>PHP license when bundled with PHP.
>>>
>>>-Rasmus
>>>
>>>--
>>>PHP Internals - PHP Runtime Development Mailing List
>>>To unsubscribe, visit: http://www.php.net/unsub.php