I don't see the point of storing an OAuthService in a cache, what's your use case?

After creating the OAuthService, I need to redirect the user to the authorization URL. After that authorization has been successful, the service will redirect the user back to my web app. Then I need the previously used OAuthService and RequestToken to obtain the Access Token and some user information.

Is there any other way to reconstruct the previously used OAuthService besides serializing in a cache ?

Thanks

You don't need to reconstruct the OAuthService, it's intended to be used as
a singleton object. It's threadsafe so you can keep a global reference to
it anywhere you like.

Pablo

On Thu, Mar 22, 2012 at 3:59 PM, Bruno Fuster <
[email protected]

wrote:

After creating the OAuthService, I need to redirect the user to the
authorization URL. After that authorization has been successful, the
service will redirect the user back to my web app. Then I need the
previously used OAuthService and RequestToken to obtain the Access Token
and some user information.

Is there any other way to reconstruct the previously used OAuthService
besides serializing in a cache ?

Thanks

---

Reply to this email directly or view it on GitHub:

#238 (comment)

Huge mistake of mine :(

Didn't know it was threadsafe