By estherschindler
via informit.com
Published: Mar 09 2010 / 09:12
Scott Seely explains when developers need to create a new endpoint versus just adding data. This higher level, non-language specific article explains how to version REST services and when each choice makes sense.
-
Code comments gone wrong
-
AppDynamics Selects ScaleBase for Database Scalability and Management
-
Introducing VMware vFabric Suite 5.1: Automated Deployment, New Components, and Open Source Support
-
Interview With Ward Cunningham
-
With Knowledge Graph, Google just got a whole lot Smarter
-
Big Data Architecture at LinkedIn
Comments
bwtaylor replied ago:
One thing that irked me is the list of reasons to version is if you make changes such as "Updating your URL structure. If you move the resource, existing clients won’t be able to get to them. "
NO! You aren't doing it right. If you are RESTful, it will NOT break if you change your URL structure. Conversely if it does break you are NOT RESTful. See the 4th bullet: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
Voters For This Link (11)
Voters Against This Link (0)