If the client provides the oauth_callback parameter when it asks for a request token then it's using the new flow. The oauth_callback parameter is required in 1.0a exactly for this reason. If the client doesn't want to provide a callback, or if the callback is provided some other way, the oauth_callback parameter's value will be 'oob' (out of band).
Mike On Thu, Aug 20, 2009 at 9:28 AM, Richer, Justin P.<[email protected]> wrote: > > I've been wondering about this as well and haven't seen any best-practices or > suggestions on the matter. All of our stuff is still 1.0-based since it seems > switching to 1.0a will close the door on the old way -- at least as far as > how most of the libraries seem to be implementing things. > > Is there a better way? Am I missing something? > > -- justin > > ________________________________________ > From: [email protected] [[email protected]] On Behalf Of Hannes > Tydén [[email protected]] > Sent: Thursday, August 20, 2009 10:46 AM > To: OAuth > Subject: [oauth] Support for 1.0 and 1.0a in parallel > > Hi > > I'm on my way to upgrade to 1.0a, but would like to keep support for > 1.0 for a while until all clients also moved on to safer ground. > > Anyone willing to share their experiences of this subject? > > Thanks, > Hannes > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
