IETF Logo Mail Archive

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

Marius Scurtescu <mscurtescu@google.com> Wed, 05 May 2010 18:18 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 B1F483A6A46 for <oauth@core3.amsl.com>; Wed, 5 May 2010 11:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.923
X-Spam-Level:
X-Spam-Status: No, score=-105.923 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 vGhACQQZKYUa for <oauth@core3.amsl.com>; Wed, 5 May 2010 11:18:21 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 775233A6A51 for <oauth@ietf.org>; Wed, 5 May 2010 11:18:20 -0700 (PDT)
Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id o45II6uh010798 for <oauth@ietf.org>; Wed, 5 May 2010 11:18:06 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273083487; bh=0U4b0BiDhdFo6K92AlkSus3uJeo=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=CFRq30xZYZ69E/wgcOdXkx74FgKM4UOUAUeEnbiX65gnuf+O510O3zYYiiQG+evar 0jEYke3cB7iQFaX0RWnmA==
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=QhX52XwY7BYPs+yl7wCTvru+nCi11KGSxx29hJC/29NTM2UEg5r6gFz4S0ywKklqG y+LcFGKB3Bi3v3uxFAUUA==
Received: from pvg2 (pvg2.prod.google.com [10.241.210.130]) by wpaz29.hot.corp.google.com with ESMTP id o45II3L0008103 for <oauth@ietf.org>; Wed, 5 May 2010 11:18:05 -0700
Received: by pvg2 with SMTP id 2so611806pvg.10 for <oauth@ietf.org>; Wed, 05 May 2010 11:18:01 -0700 (PDT)
Received: by 10.140.83.9 with SMTP id g9mr5867166rvb.6.1273083480436; Wed, 05 May 2010 11:18:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.14.15 with HTTP; Wed, 5 May 2010 11:17:40 -0700 (PDT)
In-Reply-To: <AANLkTilA40XmbIShf3m139IodJRCWUvAouyuHbWcgga7@mail.gmail.com>
References: <9890332F-E759-4E63-96FE-DB3071194D84@gmail.com> <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> <AANLkTilA40XmbIShf3m139IodJRCWUvAouyuHbWcgga7@mail.gmail.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 05 May 2010 11:17:40 -0700
Message-ID: <AANLkTimaQsJGf-GHWYa486GNKquhZaRPjwzGxdqp4Viv@mail.gmail.com>
To: Evan Gilbert <uidude@google.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 18:18:22 -0000

On Wed, May 5, 2010 at 10:06 AM, Evan Gilbert <uidude@google.com> wrote:
>
> ... and JSON only adds complexity and external
> library requirements.
>
> I'm not positive we need to support JSON at all.

Tend to agree.

Other than being nice, what other advantages does JSON provide?

Keep in mind that most people voted for one format only, and that is
clearly not possible, at a minimum we have to support both
application/x-www-form-urlencoded and JSON.

Marius

v2.15.0 | Report a Bug | By Email