://api.facebook.com/restserver.php?&callback=FB.RestServer._callback&access_token=ACCESS_TOKEN
>
> The "callback" parameter is used pretty universally for JSONP requests. For
> instance, see the Jquery docs: http://api.jquery.com/jQuery.getJSON/
>
> -Original Mess
i.facebook.com/restserver.php?&callback=FB.RestServer._callback&access_token=ACCESS_TOKEN
> >
> > The "callback" parameter is used pretty universally for JSONP requests.
> For instance, see the Jquery docs: http://api.jquery.com/jQuery.getJSON/
> >
> >
elated note, I think it's more confusing calling it something
> > different in the user-agent flow (redirector) when it's essentially
> > doing the same thing.
> >
> >
> > From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On
> > Behalf Of Eran Hamm
; The "callback" parameter is used pretty universally for JSONP requests. For
> instance, see the Jquery docs: http://api.jquery.com/jQuery.getJSON/
>
> -Original Message-
> From: Richard Barnes [mailto:rbar...@bbn.com]
> Sent: Friday, April 16, 2010 9:10 AM
> To: Luke
ewhere so whatever) seems
> the best to me too.
>
I'm fine with either.
>
> -Original Message-
> From: Richard Barnes [mailto:rbar...@bbn.com]
> Sent: Friday, April 16, 2010 12:27 PM
> To: Evan Gilbert
> Cc: Luke Shepard; Naitik Shah; OAuth WG
> Subjec
Auth WG
Subject: Re: [OAUTH-WG] Rename callback => callback_uri
Ok, I think I get it. Thanks for the explanation.
It seems we have a collision of layers here! When OAuth parameters
are being passed as request parameters (GET or POST), they can collide
with parameters being used by an appl
ess token as well, then
>> it would look like:
>>
>>
>> https://api.facebook.com/restserver.php?&callback=FB.RestServer._callback&access_token=ACCESS_TOKEN
>>
>> The "callback" parameter is used pretty universally for JSONP requests.
>> For ins
ack&access_token=ACCESS_TOKEN
The "callback" parameter is used pretty universally for JSONP
requests. For instance, see the Jquery docs: http://api.jquery.com/jQuery.getJSON/
-Original Message-
From: Richard Barnes [mailto:rbar...@bbn.com]
Sent: Friday, April 16, 2010 9
age-
> From: Richard Barnes [mailto:rbar...@bbn.com]
> Sent: Friday, April 16, 2010 9:10 AM
> To: Luke Shepard
> Cc: Eran Hammer-Lahav; Naitik Shah; OAuth WG
> Subject: Re: [OAUTH-WG] Rename callback => callback_uri
>
> Could you clarify a little more the environment in w
nce, see the Jquery docs: http://api.jquery.com/jQuery.getJSON/
-Original Message-
From: Richard Barnes [mailto:rbar...@bbn.com]
Sent: Friday, April 16, 2010 9:10 AM
To: Luke Shepard
Cc: Eran Hammer-Lahav; Naitik Shah; OAuth WG
Subject: Re: [OAUTH-WG] Rename callback => callback_u
hen it’s essentially
doing the same thing.
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On
Behalf Of Eran Hammer-Lahav
Sent: Thursday, April 15, 2010 5:37 AM
To: Naitik Shah; OAuth WG
Subject: Re: [OAUTH-WG] Rename callback => callback_uri
I don’t think it is that conf
ursday, April 15, 2010 5:37 AM
> To: Naitik Shah; OAuth WG
> Subject: Re: [OAUTH-WG] Rename callback => callback_uri
>
>
>
> 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
>
ally doing the same thing.
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Eran
Hammer-Lahav
Sent: Thursday, April 15, 2010 5:37 AM
To: Naitik Shah; OAuth WG
Subject: Re: [OAUTH-WG] Rename callback => callback_uri
I don't think it is that confusing. Its a completely d
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" wrote:
With the simplified params, the callback url parameter is now just "callback".
Since
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
15 matches
Mail list logo
