Re: [OAUTH-WG] Rename callback => callback_uri

Eran Hammer-Lahav <eran@hueniverse.com> Thu, 15 April 2010 12:41 UTC

Return-Path: <eran@hueniverse.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 D21C328C247 for <oauth@core3.amsl.com>; Thu, 15 Apr 2010 05:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level:
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 dWRt0+nXXNOe for <oauth@core3.amsl.com>; Thu, 15 Apr 2010 05:41:20 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id DDE5528C262 for <oauth@ietf.org>; Thu, 15 Apr 2010 05:37:10 -0700 (PDT)
Received: (qmail 8725 invoked from network); 15 Apr 2010 12:37:04 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 15 Apr 2010 12:37:04 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Thu, 15 Apr 2010 05:37:04 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Naitik Shah <naitik@facebook.com>, OAuth WG <oauth@ietf.org>
Date: Thu, 15 Apr 2010 05:37:02 -0700
Thread-Topic: [OAUTH-WG] Rename callback => callback_uri
Thread-Index: AcrY5QgYzwsqKHvhTbuKpWjgY2XeCgDs1Dqn
Message-ID: <C7EC567E.322EE%eran@hueniverse.com>
In-Reply-To: <9C30AE64-7DB8-4B6B-879B-61CB71BF74BB@facebook.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7EC567E322EEeranhueniversecom_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Rename callback => callback_uri
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: Thu, 15 Apr 2010 12:41:24 -0000

I don't think it is that confusing. Its a completely different context from where JSON-P is used (note that in the User-Agent flow it is called something else).

EHL


On 4/10/10 12:35 PM, "Naitik Shah" <naitik@facebook.com> wrote:

With the simplified params, the callback url parameter is now just "callback". Since most major API providers already use "callback" to signify JSON-P callback, can we rename this to "callback_uri"? This will help avoid collisions and confusion.


-Naitik
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth