If you don't need to access the API as the user in between sessions then
currently no.
On Fri, Mar 27, 2009 at 12:00, Chris wrote:
>
> So say I send them through the OAuth flow everytime, would there then
> be any reason to persist their access tokens in the DB? as I could
> just save it to the
So say I send them through the OAuth flow everytime, would there then
be any reason to persist their access tokens in the DB? as I could
just save it to the session when they run through the flow again.
On Mar 27, 9:39 am, Abraham Williams <4bra...@gmail.com> wrote:
> 2 options:
> 1) Roll your ow
Hi there,
Just to let everybody know, I'm currently working on a way for
you to use Twitter for login without getting back a new access token
every time. The database churn is not good for performance, and the re-
authorize is a crappy user experience. It's really a lose-lose at the
mo
2 options:
1) Roll your own authentication or use something like OpenID, Facbook
Connect, etc.
2) Send the users through the OAuth flow every time they visit your site.
Abraham
On Fri, Mar 27, 2009 at 02:29, Chris wrote:
>
> Hey guys, this is probably a pretty basic question - but somehow I
> h
