p
/
json-rpc-shell
1
1
Fork 0
Code Issues 8 Pull Requests Projects 1 Releases 2 Wiki Activity

WebSockets are no longer experimental 

Now that I've made it work at all, at least in some cases.
This commit is contained in:
Přemysl Eric Janouch 2017-02-06 21:13:59 +01:00
parent 9531f2b518
commit c03af00e30
Signed by: p
GPG Key ID: B715679E3A361BE6
2 changed files with 2 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.adoc
View File

@ -27,9 +27,8 @@ Supported transports
WebSockets WebSockets
~~~~~~~~~~ ~~~~~~~~~~
The WebSocket transport is rather experimental. As the JSON-RPC 2.0 spec The JSON-RPC 2.0 spec doesn't say almost anything about underlying transports.
doesn't say almost anything about the underlying transports, I'll shortly The way it's implemented here is that every request is sent as a single text
describe the way it's implemented: every request is sent as a single text
message. If it has an "id" field, i.e. it's not just a notification, the 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. client waits for a message from the server in response.

4
json-rpc-shell.c
View File

@ -3432,11 +3432,7 @@ main (int argc, char *argv[])
g_ctx.backend = backend_curl_new (&g_ctx, endpoint); g_ctx.backend = backend_curl_new (&g_ctx, endpoint);
else if (!strcasecmp_ascii (url_schema, "ws") else if (!strcasecmp_ascii (url_schema, "ws")
|| !strcasecmp_ascii (url_schema, "wss")) || !strcasecmp_ascii (url_schema, "wss"))
{
print_warning ("WebSocket support is experimental"
" and most likely completely broken");
g_ctx.backend = backend_ws_new (&g_ctx, endpoint, &url); g_ctx.backend = backend_ws_new (&g_ctx, endpoint, &url);
}
else else
exit_fatal ("unsupported protocol"); exit_fatal ("unsupported protocol");
free (url_schema); free (url_schema);