diff options
author | Přemysl Janouch <p.janouch@gmail.com> | 2017-02-06 21:13:59 +0100 |
---|---|---|
committer | Přemysl Janouch <p.janouch@gmail.com> | 2017-02-06 21:28:40 +0100 |
commit | c03af00e300b6f70d88118ebd1f56c2421efe20f (patch) | |
tree | 4da8f23ef4f2d0a1fb9e5b13805bb5c14f8eb0b5 /README.adoc | |
parent | 9531f2b5184e12cdea95b356c842b9b19fbc80fb (diff) | |
download | json-rpc-shell-c03af00e300b6f70d88118ebd1f56c2421efe20f.tar.gz json-rpc-shell-c03af00e300b6f70d88118ebd1f56c2421efe20f.tar.xz json-rpc-shell-c03af00e300b6f70d88118ebd1f56c2421efe20f.zip |
WebSockets are no longer experimental
Now that I've made it work at all, at least in some cases.
Diffstat (limited to 'README.adoc')
-rw-r--r-- | README.adoc | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/README.adoc b/README.adoc index f8de148..c18eb67 100644 --- a/README.adoc +++ b/README.adoc @@ -27,9 +27,8 @@ Supported transports WebSockets ~~~~~~~~~~ -The WebSocket transport is rather experimental. As the JSON-RPC 2.0 spec -doesn't say almost anything about the underlying transports, I'll shortly -describe the way it's implemented: every request is sent as a single text +The JSON-RPC 2.0 spec doesn't say almost anything about underlying 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. |