The basic flow for a desktop app is: 1: app gets token from twitter behind the scenes. 2: sends user to twitter in browser with part of request token in querystring. 3: user approves access on twitter. 4: user comes back to app and clicks on a continue button. 5: app behind the scene trades request token for access token. 6: app saves access token and interacts with the API.
A good example to look at is Flickr's Uploadr app. Abraham 2009/3/16 Joshua Perry <[email protected]> > > I am attempting to get our desktop Twitter application ready for OAuth; > we were not in the business of creating an application when the OAuth > beta happened or we probably would have applied to join. > > Is Twitter going to be using querystring, cookie, or the form field > based method of passing the access token? > > Are there any gotchas with Twitter OAuth that I may want to take into > account? > > I looked through the Ruby example but most of the functionality is down > in the OAuth gem. > > Josh > -- Abraham Williams | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from: Madison Wisconsin United States.
