openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #04733
Re: OpenStack API Versioning Conventions
On Oct 12, 2011, at 11:26 AM, Soren Hansen wrote:
> 2011/10/11 George Reese <george.reese@xxxxxxxxxxxxx>:
>> See EC2 for someone doing it damn well. I've never had to write new code to talk to them unless I want to take advantage of new functionality.
>
> Now I'm confused. EC2 includes the API version in the URI, but I
> thought you were opposed to that?
>
>
No, EC2 includes the version in the parameters. That's not the right place for them either, but keep in mind that the EC2 API is not a RESTful API and should not be used as a reference for RESTful structure.
Here, I was using it as an example not of RESTful structure, but instead how an API of any structure should handle past versions.
-George
--
George Reese - Chief Technology Officer, enStratus
e: george.reese@xxxxxxxxxxxxx t: @GeorgeReese p: +1.207.956.0217 f: +1.612.338.5041
enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http://www.enstratus.com
To schedule a meeting with me: http://tungle.me/GeorgeReese
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
References
-
OpenStack API Versioning Conventions
From: Brian Waldon, 2011-10-10
-
Re: OpenStack API Versioning Conventions
From: Mark Nottingham, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: Bryan Taylor, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: Brian Waldon, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: George Reese, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: Brian Waldon, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: George Reese, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: Brian Waldon, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: George Reese, 2011-10-11
-
Re: OpenStack API Versioning Conventions
From: Soren Hansen, 2011-10-12