IETF Logo Mail Archive

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

Marius Scurtescu <mscurtescu@google.com> Wed, 05 May 2010 15:50 UTC

Return-Path: <mscurtescu@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 0F21F3A686D for <oauth@core3.amsl.com>; Wed, 5 May 2010 08:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.409
X-Spam-Level:
X-Spam-Status: No, score=-100.409 tagged_above=-999 required=5 tests=[AWL=-0.846, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, 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 ZDH3jT9rEp9C for <oauth@core3.amsl.com>; Wed, 5 May 2010 08:50:04 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 12AAA28C38A for <oauth@ietf.org>; Wed, 5 May 2010 08:43:08 -0700 (PDT)
Received: from kpbe13.cbf.corp.google.com (kpbe13.cbf.corp.google.com [172.25.105.77]) by smtp-out.google.com with ESMTP id o45FgrOH025358 for <oauth@ietf.org>; Wed, 5 May 2010 08:42:54 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273074174; bh=UfN4/PEL/GDKBssWnKNKfSdUpe8=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=N9XlJz0YLsA54YtY3eEsMAuKpUAipqJDCMNqCMUKrAsbx6Hyc8MpcaVTvjaPv9Lhc 5iCujWStL+yfDmGTBSoGQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=BLG9gUjsuuVN5En52p6R+2hT6s7iZ/DA26FGhikdddMN6xN3QvcyePK/qPejHp4QA K3HmBLFpdaD+N3MGHvyHA==
Received: from pxi10 (pxi10.prod.google.com [10.243.27.10]) by kpbe13.cbf.corp.google.com with ESMTP id o45FgpIT014236 for <oauth@ietf.org>; Wed, 5 May 2010 08:42:52 -0700
Received: by pxi10 with SMTP id 10so2735476pxi.7 for <oauth@ietf.org>; Wed, 05 May 2010 08:42:51 -0700 (PDT)
Received: by 10.140.88.33 with SMTP id l33mr5684194rvb.4.1273074171133; Wed, 05 May 2010 08:42:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.14.15 with HTTP; Wed, 5 May 2010 08:42:31 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723439323D0DB0@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <9890332F-E759-4E63-96FE-DB3071194D84@gmail.com> <4BD8869A.2080403@lodderstedt.net> <s2zc334d54e1004281425x5e714eebwcd5a91af593a62ac@mail.gmail.com> <v2j68fba5c51004282044o3a5f96cfucb1157d3884d8cd2@mail.gmail.com> <4BD9E1E3.7060107@lodderstedt.net> <7C01E631FF4B654FA1E783F1C0265F8C4A3EF0B0@TK5EX14MBXC115.redmond.corp.microsoft.com> <z2yf5bedd151004291440g17693f8du9e19a649bef925e4@mail.gmail.com> <w2odaf5b9571004291509x8895a73k384a4b4ddb12b794@mail.gmail.com> <20100430105935.20255m8kdythy6sc@webmail.df.eu> <90C41DD21FB7C64BB94121FBBC2E723439323D0DB0@P3PW5EX1MB01.EX1.SECURESERVER.NET>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 05 May 2010 08:42:31 -0700
Message-ID: <AANLkTik3NSJynWfiNWovruPEOT2Y6G1zcWPFOaS_pHdy@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "oauth@ietf.org" <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: Wed, 05 May 2010 15:50:05 -0000

On Wed, May 5, 2010 at 8:28 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> I'll add something to the draft and we'll discuss it. There is enough consensus on a single JSON response format.

Yesterday I got the following feedback:

On Tue, May 4, 2010 at 5:43 PM, Greg Robbins <grobbins@google.com> wrote:
> Using JSON on the iPhone requires developers to drag in source code for a
> third-party library.
>
> If their app isn't already relying on JSON for some other purpose, then
> adding a third-party library is a somewhat substantial annoyance,
> particularly for a mobile app where code size is important.
>
> If OAuth 2 is only intended for use with JSON APIs, then returning all
> responses as JSON is reasonable. Otherwise, it's not so reasonable. A full
> JSON parser is non-trivial, and seems like overkill for simple responses.
>
> The iPhone OS does have libxml2 and an event-style XML parser, but no really
> easy way to extract data from XML, either.
>
> Form-style responses are much more straightforward to worth with given
> simple string-manipulation utilities.

If the above is true, then I am not so sure about JSON anymore. Lots
of phones and devices will have problems with it.

Marius

v2.15.0 | Report a Bug | By Email