Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68666 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70180 invoked from network); 29 Aug 2013 06:25:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Aug 2013 06:25:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.91 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.91 smtp91.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.91] ([108.166.43.91:35844] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 24/B2-57841-969EE125 for ; Thu, 29 Aug 2013 02:25:45 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 55B4B140117; Thu, 29 Aug 2013 02:25:42 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id F393B14009B; Thu, 29 Aug 2013 02:25:41 -0400 (EDT) Message-ID: <521EE964.4080506@sugarcrm.com> Date: Wed, 28 Aug 2013 23:25:40 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Remi Collet CC: PHP Internals References: <521EE223.9060702@fedoraproject.org> In-Reply-To: <521EE223.9060702@fedoraproject.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Switch from json extension to jsonc [Discussion] From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Subject: Switch from json extension which have a problematic (non-free) > license to jsonc dropin free alternative. > > RFC: https://wiki.php.net/rfc/free-json-parser From what I see in the benchmarks, while encoding is on par with current implementation, decoding is more than 2x slower. This may be a problem, especially for something like REST API that may have to decode decent amount of JSON data. Can it be fixed? Also, I see the sizes of the encode results is different from ext/json. Why is that? Also, "Partial implementation of big integers parsing" is a bit worrying. If we want to have drop-in replacement, partial implementations would lead to trouble. Can it be fixed? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227