IETF Logo Mail Archive

Re: [OAUTH-WG] application/x-www-form-urlencoded vs JSON (Proposal)

Brian Eaton <beaton@google.com> Mon, 10 May 2010 21:46 UTC

Return-Path: <beaton@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4466A3A69DC for <oauth@core3.amsl.com>; Mon, 10 May 2010 14:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.313
X-Spam-Level:
X-Spam-Status: No, score=-104.313 tagged_above=-999 required=5 tests=[AWL=-1.350, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Km74pCXFW5HY for <oauth@core3.amsl.com>; Mon, 10 May 2010 14:46:06 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 5A6353A6902 for <oauth@ietf.org>; Mon, 10 May 2010 14:46:06 -0700 (PDT)
Received: from hpaq5.eem.corp.google.com (hpaq5.eem.corp.google.com [172.25.149.5]) by smtp-out.google.com with ESMTP id o4ALjoAL017376 for <oauth@ietf.org>; Mon, 10 May 2010 14:45:51 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273527951; bh=GUJ1S3UfnUMCKoTIe94zGaGH1qs=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=GIjME7/61lAW1tfC8PCmZp6OcvLLczvgQQf3jNbdKR469/MGtzonL9UEgKpI1e440 6f4BCyITGQxGqFqnZAhCg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=rklXE1DE/EgzUmnYbwBbcDAJDXejiPtA0n7byiG5h5F6lhOkJL6hmlve6MvHwgZIm 47rlmGcU6K3aEOkJ8Q/eg==
Received: from pzk35 (pzk35.prod.google.com [10.243.19.163]) by hpaq5.eem.corp.google.com with ESMTP id o4ALjmEG000544 for <oauth@ietf.org>; Mon, 10 May 2010 14:45:49 -0700
Received: by pzk35 with SMTP id 35so1710219pzk.0 for <oauth@ietf.org>; Mon, 10 May 2010 14:45:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.25.38 with SMTP id c38mr3092606wfj.251.1273527947984; Mon, 10 May 2010 14:45:47 -0700 (PDT)
Received: by 10.143.136.7 with HTTP; Mon, 10 May 2010 14:45:47 -0700 (PDT)
In-Reply-To: <10577de84bc497dea170055097bc0086@mail.gmail.com>
References: <9890332F-E759-4E63-96FE-DB3071194D84@gmail.com> <AANLkTil2_9KOm1eRoC0jxvH99E55K3BEW-T5cgWLay9H@mail.gmail.com> <AANLkTilWV3VVBROXZuky5OLNzM2hz27pEqwG1l6W2Uc1@mail.gmail.com> <4BE1BB10.7060009@lodderstedt.net> <w2v77facc501005051149pca35de47tfcca515a3b557c81@mail.gmail.com> <4BE1F2A1.9040707@pidster.com> <s2mc334d54e1005060846k10f446b4r5f907acf237f8735@mail.gmail.com> <01bb1f595f89af50b0c37c00dbcd54cd@mail.gmail.com> <E9F67F8B-DF87-40D5-8BCF-F9113D14BD77@facebook.com> <10577de84bc497dea170055097bc0086@mail.gmail.com>
Date: Mon, 10 May 2010 14:45:47 -0700
Message-ID: <AANLkTikAYonxhBbSKvuVRegZykTDmASInXIgbk5Z1Ksa@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Greg Brail <gbrail@sonoasystems.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] application/x-www-form-urlencoded vs JSON (Proposal)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 May 2010 21:46:07 -0000

On Fri, May 7, 2010 at 11:29 AM, Greg Brail <gbrail@sonoasystems.com> wrote:
> JSONObject is fine. I imagine that any development organization could use it
> in their project as long as their legal staff is willing to forgo the option
> of doing Evil. (That's what the license says ;-)

If the issue is purely the quirky licensing of the org.json code, gson
should be an option:

http://code.google.com/p/google-gson/

Cheers,
Brian

v2.23.0 | Report a Bug | By Email