Backlog #2341
Optionally output JSON from the API
| Status: | Closed | Start date: | 09/26/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - |
Description
In order to facilitate easier client writing (and for better efficiency on large lists of VMs), I would like to optionally receive data from the API In JSON instead of XML. I understand that the current VM data is stored in a NoSQL-like fashion as a pre-built XML, maybe an option would be to store the JSON in a seperate column and also prebuild it on every update together with the XML? The data is in memory and structured correctly at the time the XML is written, so it might be very simple to convert it to JSON and save it together with the XML.
History
#1
Updated by Ruben S. Montero over 7 years ago
- Status changed from Pending to New
#2
Updated by Ruben S. Montero over 7 years ago
- Tracker changed from Feature to Backlog
- Status changed from New to Pending
I agree with your possible implementation. The main concern would be the overhead to generate both documents. On the other hand it would help javascript applications.
In the meantime, you have a set of *JSON classes in the Ruby API that deals with it.
#3
Updated by Ruben S. Montero over 7 years ago
- Category set to Core & System
#4
Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to Closed
We'll keep this in the OCA level.