This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Web Services Certification (SCDJWS/OCEJWSD) and the fly likes why did google, amazon, github etc choose uri versioning for their rest apis? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Certification » Web Services Certification (SCDJWS/OCEJWSD)
Bookmark "why did google, amazon, github etc choose uri versioning for their rest apis?" Watch "why did google, amazon, github etc choose uri versioning for their rest apis?" New topic
Author

why did google, amazon, github etc choose uri versioning for their rest apis?

Sandeep Pr
Greenhorn

Joined: Aug 15, 2013
Posts: 1
Hi All,

I am reading a lot on the ReST these days and i am stuck at one point. I understand the pros and cons of 'uri-versioning' vs 'content-negotiation' for version management, but i keep reading on every blog or forum that google, amazon etc choose to go for 'uri versioning'. i am just wondering WHAT could be the reason behind it.
Can some one throw some light on this?

regards,
Sandeep P
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: why did google, amazon, github etc choose uri versioning for their rest apis?
 
It's not a secret anymore!