The callback isn't done server-side. Instead, it simply tells the
browser to visit a certain URL.

I personally don't like the usage of the word Callback here. I would say
that "Return URL" would be a better word. However, the OAuth spec disagrees.

Tom


On 9/26/10 10:42 AM, CI-CUBE wrote:
> I'm really surprised that twitter oauth negotiation works with
> localhost callbacks... neither I've authorized localhost as callback
> domain nor do I understand how this is possible technically...
> 
> Any comments please? Love to learn...
> 
>   Ekki
> 
> * GWT Rocks! * SmartGWT Rocks Even Harder! * GWT 2.0.3,
> SmartGWT PRO 2.3, JRE 1.6.0_20, Eclipse 3.6 *
> * Xcode 3.2.2 * iOS 3.0 (Base OS) *
> 

-- 
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

Reply via email to