Open Stack

Everett Toews wrote:
> I agree that more metrics are needed before condemning the XML API. That 30% number from user survey might not have a lot of detail behind it but we need to respect those users who are actually using it. Breaking client code is not a good developer experience.

This proposal is not "breaking" client code... Client code working with
v2 XML will happily continue to work until v2 is fully removed.

Like Russell said, remember this is about the next major API version,
which introduces a number of non-backwards compatible changes. So
"client code" (XML or JSON) will need to adapt to support it, that's
what the transition period is for.

I agree that people using XML-based v2 client code will have a steeper
transition to v3 than those using JSON-based v2 client code. But given
the data we have so far (actual usability of the XML v2 API, number of
users of pure XML, existing language bindings), it sounds like a
reasonable trade-off. Like I said before, I prefer to have no XML
support rather than a bad one, and removing it will allow us to do a
better job with the remaining APIs (JSON v3 API, EC2 API...).

-- 
Thierry Carrez (ttx)