[rest-practices] Versioning

[Bob McWhirter]

Isn't this where the other week's discussion on content-types, content  
negotiation, and Accept: headers figure in?  The API and the model of  
the resources is one-in-the-same, really, no?  The "API" is just a  
root synthetic collection or object, sometimes, versionable like any  
other model entity using content-type.

	-Bob



On Apr 26, 2010, at 9:52 AM, Mark McLoughlin wrote:

> Hey,
>
> On Mon, 2010-04-26 at 08:32 -0400, Bryan Kearney wrote:
>> Following up on the earlier thread... if the preferred model to put
>> version information in the media type, or in the url?
>>
>> And.. if in the url, are you starting with a 1 to begin with or if  
>> the
>> absence of a number a version 1?
>
> "Version in url and no version means version 1" makes most sense to me
> so far:
>
>  https://www.redhat.com/archives/rest-practices/2010-April/msg00014.html
>
>    version negotiation is done by the client choosing between e.g.
>
>      <link rel="vms" href="...." />
>      <link rel="vms_v2" href="..." />
>
> Cheers,
> Mark.
>
> _______________________________________________
> rest-practices mailing list
> rest-practices at redhat.com
> https://www.redhat.com/mailman/listinfo/rest-practices