dev
Subject: Re: Default API response type: XML -> JSON
No problem Marc, but I still do not think that having a parameter is an
overkill. My view is that if there is a decision to be made (regarding the
default response type for requests), if we (as developers) take this
decision (ha
I am +1 but with a versioned API (v2) because this would break most
likely many API implementations.
René
On 04/23/2018 03:34 PM, Marc-Aurèle Brothier wrote:
> Hi everyone,
>
> I thought it would be good to move from XML to JSON by default in the
> response of the API if no response type is
The time would be better spent on fixing the docs.
It is time to turn Cloudstack into a production quality product with
documentation that actually reflects the quality of the design and
functionality.
At the moment you have 2 people willing to work on the docs waiting for
a committer to
No problem Marc, but I still do not think that having a parameter is an
overkill. My view is that if there is a decision to be made (regarding the
default response type for requests), if we (as developers) take this
decision (hardcode it), why not externalize it? I do not see as overkill,
it is a
@rafael - I think it's overkill to have this as a configuration option. We
should have one default response type, or maybe not have a default one and
enforce the use of the response type the client is willing to receive.
On Mon, Apr 23, 2018 at 3:39 PM, Rafael Weingärtner <
I do think it is an interesting proposal. I have been thinking, and what if
we do something different; what about a global parameter where the root
admin can define the default serialization mechanism (XML, JSON, RDF,
others...)? The default value could be XML to maintain backward
compatibility.
Hi everyone,
I thought it would be good to move from XML to JSON by default in the
response of the API if no response type is sent to the server along with
the request. I'm wondering that's the opinion of people on the mailing list.
Moreover, if anyone knows a tool working with the API in XML
