you can refer to the demo program "gridtwit": http://code.google.com/p/gridtwit/
especially the files: "gridtwit_client_oauth_demo\Demo_Description.doc" and "gridtwit_client_oauth_demo\liboauth-0.9.1\tests\gridtwit.c" It details oauth authentication flow and coding(c++, liboauth). -------------------------------------------------------------------------------------------------- 2010/9/23 Taylor Singletary <taylorsinglet...@twitter.com> > Our system is quirky. There technically isn't a boolean flag set on an > application that dictates whether it's a "web" or "desktop" application -- > instead the boolean is a derived value based on the presence of a default > callback URL. Think of this callback URL as a placeholder -- while it should > have some relevance to your application, it doesn't need to strictly > correlate to an actual callback location. To practice "correct" OAuth, you > still need to provide an oauth_callback on the request token step of the > OAuth negotiation phase. The callback provided at that time always > takes precedence. > > Taylor > > > On Thu, Sep 23, 2010 at 12:23 AM, Scott Wilcox <sc...@dor.ky> wrote: > >> Yes, you can dynamically provide a callback URL, but you still need to >> enter one in the applications settings. >> >> Scott. >> >> On 23 Sep 2010, at 07:34, kengimel wrote: >> >> > Hi, >> > >> > I recently register my twitter application and obtained my OAuth >> > consumer credentials. >> > >> > However i noticed that when registering i choose the browser option as >> > my application will run solely via a web browser, But to my surprise >> > when i dispatched this: POST https://twitter.com/oauth/request_token, >> > I recieved this error mesage from my console. >> > >> > <?xml version="1.0" encoding="UTF-8"?> >> > <hash> >> > <request>/oauth/request_token</request> >> > <error>Desktop applications only support the oauth_callback value >> > 'oob'</error> >> > </hash> >> > >> > I have tried several times to select the browser option on my >> > application's settings page, but it says it requires me to define a >> > callback URL, which according to the OAuth standard, allows me to >> > dynamically define my callback URL in the request token stage. >> > >> > can someone tell me what i may be doing wrongly. >> > >> > Cheers >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
