mirror of
https://github.com/adulau/pdns-qof.git
synced 2024-11-22 10:07:09 +00:00
Clarification regarding the JSON object per line.
This commit is contained in:
parent
d05dfc1e06
commit
da7f22039f
1 changed files with 1 additions and 1 deletions
|
@ -171,7 +171,7 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
|
||||||
<section title="Common Output Format">
|
<section title="Common Output Format">
|
||||||
<section title="Overview">
|
<section title="Overview">
|
||||||
<t>The formatting of the answer follows the <xref target="RFC4627">JSON</xref> format. The order of the fields is not significant for the same resource type. That means, the same name tuple plus timing information identifies a unique answer per server.</t>
|
<t>The formatting of the answer follows the <xref target="RFC4627">JSON</xref> format. The order of the fields is not significant for the same resource type. That means, the same name tuple plus timing information identifies a unique answer per server.</t>
|
||||||
<t>The intent of this output format is to be easily parsable by scripts. Every implementation MUST support the JSON output format.</t> <!-- note: it is "parsable" if you want to be really nit-picking. See: https://en.wiktionary.org/wiki/parsable -->
|
<t>The intent of this output format is to be easily parsable by scripts. Each JSON object is expressed on a single line to be processed by the client line-by-line. Every implementation MUST support the JSON output format.</t> <!-- note: it is "parsable" if you want to be really nit-picking. See: https://en.wiktionary.org/wiki/parsable -->
|
||||||
</section>
|
</section>
|
||||||
<section title="Example">
|
<section title="Example">
|
||||||
<figure><preamble>A sample output using the JSON format:</preamble><artwork><![CDATA[
|
<figure><preamble>A sample output using the JSON format:</preamble><artwork><![CDATA[
|
||||||
|
|
Loading…
Reference in a new issue