why did google, amazon, github etc choose uri versioning for their rest apis?
posted 3 years ago
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?