RESTful API Resources

Dmitri Dolguikh dmitri at redhat.com
Thu Nov 8 13:51:27 UTC 2012


On 08/11/12 01:30 PM, Justin Clift wrote:
> On 08/11/2012, at 2:09 PM, Dmitri Dolguikh wrote:
>> On 08/11/12 12:59 PM, Justin Clift wrote:
>>> On 08/11/2012, at 1:45 PM, Dmitri Dolguikh wrote:
>>>> Any opinion on versioning via mime-types, ie: Content-Type: application/xml; version=1.0?
>>>> This results in non-versioned resource urls, which IMHO is beneficial.
>>> Doesn't that make it impossible to use a standard http link
>>> (ie on a web page interface) to use a specific version?
>>>
>>> Selecting the version number through the request header seems
>>> like it would limit things to applications only.
>>>
>>> ?
>> Wouldn't you always want to retrieve the latest version of the resource when using a web browser? You have control over http request headers when using js too.
> Errr, no.  If I'm used to doing things with version X, then
> I want to keep on using version X instead of things changing
> (perhaps significantly) without warning.
>
> Letting people change when they're ready to is generally a
> better idea than forcing our schedule on them.  (as a
> general concept :>)
>
> + Justin

Some clients might be interested in using a specific version of resource 
representation, others might always want to use the latest. Adding 
versioning to resource urls makes discoverability harder, and requires 
the client to understand resource url format.

-d
>
>> -d
>>
>>> + Justin
>>>
>>> --
>>> Aeolus Community Manager
>>> http://www.aeolusproject.org
>>>
> --
> Aeolus Community Manager
> http://www.aeolusproject.org
>




More information about the aeolus-devel mailing list