Ability to disable sockjs fallback

[sandstrom]

We like Pusher, it's awesome!

What's also awesome is that web sockets is supported in the latest version of IE, FF, Chrome, iOS and Android. Hence, we don't need the fallbacks and because of that we can also skip the dependency loading pain.

It would be great if sockjs could be disabled similar to the flash fallback.

var pusher = new Pusher(PUSHER_KEY, { disableFlash: true, disableSockjs: true });

We're doing this right now, which seems to work, but that could change with an update to the client so an option would be great.

Pusher.SockJSTransport.isSupported = function() { return false; };

[pl]

I agree, the current solution is far from perfect. In your case, it might be better to whitelist transports than to blacklist them. We might be introducing some new transports and if you just blacklist SockJS and Flash, you might end up with some fallbacks enabled anyway, which is not what you'd really want. Whitelisting WebSockets would work fine in your case and you wouldn't change anything when updating pusher-js.

[sandstrom]

Sounds good! How do I go about whitelisting them? I cannot find anything in the source (searching for white finds nothing).

[pl]

It's not supported, I was thinking whether to replace this issue with implementing a transport whitelist.

[pl]

Released today in 2.1.4 (enabledTransports and disabledTransports options). Closing, thanks for the issue.

[sandstrom]

Awesome! ⛵

(perhaps you should deprecated the disableFlash option, for clarity)

[pl]

It will be deprecated in 2.2 and removed in 3.0.

[sandstrom]

Nice! Just tried 2.1.4, works great!