Change subprotocol names

Use domain names, as suggested in https://www.rfc-editor.org/rfc/rfc6455#section-1.9.

As documented in https://www.rfc-editor.org/rfc/rfc6455#section-4.1, `/` isn't valid in a subprotocol name. (This restriction is enforced by the ws package; see https://github.com/websockets/ws/blob/8.5.0/lib/websocket.js#L34.)

Author: joshkel

README.md

@@ -105,7 +105,7 @@ const WebSocket     = require("ws")
                 websocket: {
                     only: true,
                     initially: true,
-                    subprotocol: "quux/1.0",
+                    subprotocol: "quux.example.com",
                     connect: ({ ctx, ws }) => {
                         ctx.to = setInterval(() => {
                             if (ws.readyState === WebSocket.OPEN)
@@ -210,7 +210,7 @@ $ wscat --connect ws://127.0.0.1:12345/baz
 < {"at":"baz","seen":{"foo":7}}
 
 # access the full-featured exclusive WebSocket route via WebSockets
-$ wscat --subprotocol "quux/1.0" --auth foo:bar --connect ws://127.0.0.1:12345/quux
+$ wscat --subprotocol "quux.example.com" --auth foo:bar --connect ws://127.0.0.1:12345/quux
 < {"cmd":"HELLO",arg:"foo"}
 > {"cmd":"PING"}
 < {"result":"PONG"}
@@ -281,7 +281,7 @@ server.route({
             websocket: {
                 only: true,
                 autoping: 10 * 1000,
-                subprotocol: "foo/1.0",
+                subprotocol: "v1.foo.example.com",
                 initially: true,
                 connect: ({ ctx, wss, ws, req, peers }) => {
                     ...

sample-server.js

@@ -72,7 +72,7 @@ const WebSocket     = require("ws")
                 websocket: {
                     only: true,
                     initially: true,
-                    subprotocol: "quux/1.0",
+                    subprotocol: "quux.example.com",
                     connect: ({ ctx, ws }) => {
                         ctx.to = setInterval(() => {
                             if (ws.readyState === WebSocket.OPEN)