Handle XML as well as JSON in ReST API

Registered by Zane Bitter on 2013-02-06

The ReST API should be capable of parsing input and returning output in XML format as well as JSON format.

The ContentEncoding and Accepts headers should be used for determining the correct input and output formats, respectively. This part should be fairly straightforward.

There may be changes required to the JSON output format in order to be able to easily produce XML from the same data. I'm not sure if there is an easy way to direct various parts of the output to be attributes vs. elements in XML.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
Steven Dake on 2013-04-03

Related branches

Whiteboard

Nobody cares: http://lists.openstack.org/pipermail/openstack-dev/2012-August/000857.html
And even people who do care only care about removing existing XML support, not about not adding new XML support: http://lists.openstack.org/pipermail/openstack-dev/2012-August/000467.html

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.