Test client library with explicit binary protocol in JSBin

[mattheworiordan]

Previously we had issues with websocket binary payloads so we need to test that this is no longer an issue

[SimonWoolf]

@mattheworiordan do you remember any particular jsbins had problems?

[mattheworiordan]

Nope, can't remember, I just know that for a period we had to explicitly disable the binary protocol in the browser because it was failing frequently.

[paddybyers]

@SimonWoolf: can you try something explicitly in jsbin (binary, force both websocket and non-websocket transports) ?

[SimonWoolf]

Tested it a bunch (using this js-bin on latest new-upgrade branch against dev-realtime), but couldn't see any differences between useBinaryProtocol true or false, on any transport, with various setting combinations.

(Did find one behaviour difference between jsbin and normal: with jsbin you get an exception if you use web_socket transport with tls:false and useTokenAuth: true. But unrelated to this so filing a new bug for it).

(don't think there's any difference with current prod either, but had difficulty consistently getting a successful connection anyway due to various other errors (see slack), so hard to be certain)

Closing this until we see this issue again.