zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Minor tweaks

This commit is contained in:
str4d 2016-09-25 22:36:44 +13:00 committed by Daira Hopwood
parent 6ea4d05e76
commit a396f5b973
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
drafts/str4d-stratum/draft1.rst
View File

@ -52,8 +52,8 @@ two-way line-based communication:
All communication for a particular session happens through a single connection,
which is kept open for the duration of the session. If the connection is broken
or either party disconnects, the active session is ended. Servers MAY support
session resuming; this is negotiated between the client and server during intial
setup.
session resuming; this is negotiated between the client and server during
initial setup (see `Session Resuming`_).
Each request or response is a JSON string, terminated by an ASCII LF character
(denoted in the rest of this specification by ``\n``). The LF character MUST NOT
@ -64,7 +64,7 @@ completely received.
Per [JSON-RPC-1.0]_, there is no requirement for the ``id`` property in requests
and responses to be unique; only that servers MUST set ``id`` in their responses
equal to that in the request they are responding to (or ``null`` for
notifications). However, it is recommended that clients use unique ids for their
notifications). However, it is RECOMMENDED that clients use unique ids for their
requests, to simplify their response parsing.
.. [JSON-RPC-1.0] JSON-RPC.org. *JSON-RPC 1.0 Specifications*.