Handle XML as well as JSON in ReST API

[Angus Salkeld]

Handle XML as well as JSON in ReST API

[Angus Salkeld (asalkeld)]

http://blog.doughellmann.com/2012/10/ods-grizzly-choosing-wsgi-framework-for.html

I think Doug was pushing "Pecan", the reason I suggest this is we would get xml for "free".

(added Doug to subscribers, maybe he can chime in).

[Doug Hellmann (doug-hellmann)]

We discussed using Pecan (http://pecan.readthedocs.org/en/latest/) and WSME (http://pypi.python.org/pypi/WSME) together. I'm supposed to rebuild the ceilometer API server as an example.

[Steven Hardy (shardy)]

Although I don't doubt there may be advantages in using Pecan, we don't need to do that in order to get XML support in the ReST API (IMO), we already have wsgi middleware which supports serializing/deserializing both XML and JSON for the CFN API, so I don't see why the same (or very similar) code won't work for the ReST API?

See heat/common/wsgi.py - the main change required AFAICS is to properly handle the content-type header in the request, since AWS does a weird thing using a "ContentType" query parameter instead.

[Doug Hellmann (doug-hellmann)]

The main work to implement this is done in the v2 API.

[Doug Hellmann (doug-hellmann)]

Oops, sorry, I thought this was a ceilometer ticket.

[Zane Bitter (zaneb)]

Replaced with https://blueprints.launchpad.net/heat/+spec/rest-xml since this is actually a feature request, not a bug.