[openstack-dev] [API] Standardizing status codes in the native API
Jay Pipes
jaypipes at gmail.com
Mon Jul 23 18:50:08 UTC 2012
On 07/23/2012 10:30 AM, Sean Dague wrote:
> This kind of change is more breaking than you think. I've seen a lot of
> web services client code over the years that just does (code == 200) as
> short hand for success. Is it the right thing to do? nope. But it worked
> for people, so is going to be seen as a breaking change by us.
>
> Given that OS API is an external API, I think question 3 is kind of
> irrelevant. We can't assume we know which clients are using it.
Right.
>> Also, the "we must maintain compat" is inconsistent with other similar
>> changes like this one merged on Friday:
>>
>> https://review.openstack.org/#/c/9993/
>
> Maybe we need to revisit that?
:( Wish I had caught that. That would fall under the category of
breaking API changes in my book -- though luckily only limited to one
extension.
> API uptake only happens if people's code using it doesn't break for
> reasons they don't understand.
Exactly.
-jay
More information about the OpenStack-dev
mailing list