mirror of
https://github.com/adulau/pdns-qof.git
synced 2024-11-22 18:17:04 +00:00
JSON is now a MUST, not a SHOULD
This commit is contained in:
parent
a1df3604f8
commit
b89d4df45c
1 changed files with 314 additions and 314 deletions
|
@ -159,7 +159,7 @@ The document does not describe the protocol (e.g. whois, HTTP REST or XMPP) used
|
||||||
Depending on the clients request, there might be one of three different answers from the server: Whois (human readable) output format (key-value), <xref target="RFC4627">JSON</xref> output and optionally Bind zone file output format. XXX FIXME: how does the client select which answer format he wants? XXX
|
Depending on the clients request, there might be one of three different answers from the server: Whois (human readable) output format (key-value), <xref target="RFC4627">JSON</xref> output and optionally Bind zone file output format. XXX FIXME: how does the client select which answer format he wants? XXX
|
||||||
</t>
|
</t>
|
||||||
<section title="JSON">
|
<section title="JSON">
|
||||||
<t>The intent of this output format is to be easily parseable by scripts. Every implementation SHOULD support the JSON output format.</t>
|
<t>The intent of this output format is to be easily parseable by scripts. Every implementation MUST support the JSON output format.</t>
|
||||||
<figure><preamble>A sample output using the JSON format:</preamble><artwork><![CDATA[
|
<figure><preamble>A sample output using the JSON format:</preamble><artwork><![CDATA[
|
||||||
... (list of )...
|
... (list of )...
|
||||||
{ "count": 97167,
|
{ "count": 97167,
|
||||||
|
|
Loading…
Reference in a new issue