diff options
| author | Přemysl Eric Janouch <p@janouch.name> | 2020-10-10 05:20:31 +0200 |
|---|---|---|
| committer | Přemysl Eric Janouch <p@janouch.name> | 2020-10-10 05:20:31 +0200 |
| commit | ee79249d23244bef4f18f542f28c465f9f50c77f (patch) | |
| tree | fd84663ebb35af760a78caac4ac4ab10abe6037d /json-rpc-shell.adoc | |
| parent | 160d23018ad46e254f3ef60dcedeacd152f3d92f (diff) | |
| download | json-rpc-shell-ee79249d23244bef4f18f542f28c465f9f50c77f.tar.gz json-rpc-shell-ee79249d23244bef4f18f542f28c465f9f50c77f.tar.xz json-rpc-shell-ee79249d23244bef4f18f542f28c465f9f50c77f.zip | |
json-rpc-shell.adoc: update WebSocket notes
https://github.com/open-rpc/client-js also uses WebSockets,
although they don't seem to support notifications (in general).
Diffstat (limited to 'json-rpc-shell.adoc')
| -rw-r--r-- | json-rpc-shell.adoc | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/json-rpc-shell.adoc b/json-rpc-shell.adoc index e5db693..e8525ad 100644 --- a/json-rpc-shell.adoc +++ b/json-rpc-shell.adoc @@ -113,8 +113,7 @@ newlines. WebSockets ~~~~~~~~~~ The JSON-RPC 2.0 specification doesn't say almost anything about underlying -transports. As far as the author is aware, he is the only person combining it -with WebSockets. The way it's implemented here is that every request is sent as +transports. The way it's implemented here is that every request is sent as a single text message. If it has an "id" field, i.e., it's not just a notification, the client waits for a message from the server in response. Should any message arrive unexpectedly, you will receive a warning. |