Hello,
1> If the consume is a mobile application then callback would
not be website url.
let if we assume that if application scheme is myapp.
then callback would be :
myapp://
will it work for alll Service Provider.????
2>
"Your consumer first obtain an request token. Then the user gets
redirect
to the service provider. If the user grants access he get redirected
with
an oauth_verifier. You can excahnge your request token to an access
token
only if you know the oauth_verifier. If you have that you can access
protected resources. "
Do u mean by this that through Oauth Verifer , it will come to know it
is not a new user ? Am i right?
On Dec 4, 5:17 pm, k42b3 <k42b...@googlemail.com> wrote:
> neo schrieb:
>
>
>
> > Service Provider issues an Unauthorized Request Token. The SP MUST
> > associate the callback URL with the request token it issues. Response
> > includes:
>
> > 1.oauth_token: the request token
> > 2.oauth_token_secret: the request token secret
> > 3.oauth_callback
>
> > What would be callback?
> > In this demo:
> >http://code.google.com/p/opensocial-java-client/
> > callback is : x-opensocial-demo-app://
>
> > what will be in the case of twitter?
> > how we will know what callback we have to give?
>
> > how the Mobile application/website will know that it is the same user
> > who has enter his credential is making the call with autorized token ?
>
> > can anyone explain with respect to mobile application and also with
> > website application that what callback we have to give there?
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "OpenSocial Application Development" group.
> > To post to this group, send email to opensocial-...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > opensocial-api+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/opensocial-api?hl=en.
>
> hi neo,
>
> The callback is an absoulte url. The user gets redirected to this url if
> he has granted or
> denied the access to the data.
>
> "what will be in the case of twitter? how we will
> know what callback we have to give?"
>
> If you are developing an consumer (and I assume) you can give an url how
> you like i.e.http://yourapp.com/yoda/callback. The url is always
> the same regardless of wich service provider you choose (twitter,
> google, etc...).
>
> "how the Mobile application/website will know that it is the same user
> who has enter his credential is making the call with autorized token ?"
>
> Your consumer first obtain an request token. Then the user gets redirect
> to the service provider. If the user grants access he get redirected with
> an oauth_verifier. You can excahnge your request token to an access token
> only if you know the oauth_verifier. If you have that you can access
> protected resources.
>
> regards
> k42b3- Hide quoted text -
>
> - Show quoted text -
--
You received this message because you are subscribed to the Google Groups
"OpenSocial Application Development" group.
To post to this group, send email to opensocial-...@googlegroups.com.
To unsubscribe from this group, send email to
opensocial-api+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/opensocial-api?hl=en.
