From 26d4d827d874204f22153c7e1fbbf6e2b49e37b8 Mon Sep 17 00:00:00 2001 From: str4d Date: Mon, 26 Sep 2016 11:20:36 +1300 Subject: [PATCH] Correct boolean methods to follow JSON-RPC 1.0 --- drafts/str4d-stratum/draft1.rst | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/drafts/str4d-stratum/draft1.rst b/drafts/str4d-stratum/draft1.rst index a0e76512..499edd39 100644 --- a/drafts/str4d-stratum/draft1.rst +++ b/drafts/str4d-stratum/draft1.rst @@ -245,7 +245,8 @@ Response:: {"id": 2, "result": AUTHORIZED, "error": "ERROR"}\n ``AUTHORIZED`` (bool) - Whether authorization succeeded. + MUST be ``true`` if authorization succeeded. Per [JSON-RPC-1.0]_, MUST be + ``null`` if there was an error. ``ERROR`` (obj) An error object. MUST be ``null`` if authorization succeeded. @@ -359,14 +360,16 @@ Result:: {"id": 4, "result": ACCEPTED, "error": "ERROR"}\n ``ACCEPTED`` (bool) - Whether the block was accepted. + MUST be ``true`` if the submission was accepted. Per [JSON-RPC-1.0]_, MUST be + ``null`` if there was an error. ``ERROR`` (obj) - An error object. MUST be ``null`` if the block was accepted. + An error object. Per [JSON-RPC-1.0]_, MUST be ``null`` if the submission was + accepted without error. - If the block was not accepted, the server MUST provide an error object - describing the reason for not accepting the block. See `Error Objects`_ for - the object format. + If the submission was not accepted, the server MUST provide an error object + describing the reason for not accepting the submission. See `Error Objects`_ + for the object format. ``client.reconnect()`` ----------------------