Hi Bronco, Authentication ISN'T the API. The API is versioned, but even version 2 of the API might still require our OAuth 1.0a implementation.
Think of the REST API as a set of resources. Version 1 of our REST API describes certain resources, responses, and development patterns. How you authenticate for those resources is outside of the concern of the resources themselves. There may be a day in the future where the OAuth end points are versioned, but they would be respective to a different version of OAuth (or other forms of authentication), not necessarily tied to the versioning scheme of the API itself. Taylor On Mon, Oct 4, 2010 at 8:52 AM, Bronco <heybro...@gmail.com> wrote: > Hi,everyone~ > > I've noticed that the API URL of OAuth is something like "http:// > api.twitter.com/oauth/request_token", it didn't contain the "VERSION", > which was different from others. > > Does twitter have any further plan to modify the OAuth API URL of > adding the "VERSION", like "http://api.twitter.com/1/oauth/ > request_token"? > > -- > 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