WebSockets are no longer experimental
Now that I've made it work at all, at least in some cases.
This commit is contained in:
		@@ -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.
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
@@ -3432,11 +3432,7 @@ main (int argc, char *argv[])
 | 
			
		||||
		g_ctx.backend = backend_curl_new (&g_ctx, endpoint);
 | 
			
		||||
	else if (!strcasecmp_ascii (url_schema, "ws")
 | 
			
		||||
		|| !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);
 | 
			
		||||
	}
 | 
			
		||||
	else
 | 
			
		||||
		exit_fatal ("unsupported protocol");
 | 
			
		||||
	free (url_schema);
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user