openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #04675
Re: OpenStack API Versioning Conventions
On Tue, Oct 11, 2011 at 9:56 AM, Brian Waldon
<brian.waldon@xxxxxxxxxxxxx> wrote:
> I'm not sure I agree with that. A URI should be a persistent reference to a resource within the context of a major version of an API. Between major versions, the URI structure can change completely (for example /servers -> /instances), destroying your persistent reference.
>
> Additionally, if we only support requests within the context of the latest minor version of an API, the major version is the only piece of information that matters. The mechanism for versioning through content types will only be valid within a single major version, as I do not want to define a spec that resides above all major versions of our api.
++
-jay
References