Problems with sockjs Fallback #99

Open
luniki opened this Issue Mar 2, 2013 · 6 comments

Comments

Projects
None yet
6 participants
Contributor

luniki commented Mar 2, 2013

Before pusher-js v1.12.4 Pusher used either WebSocket or Flash as a fallback. Since pusher/pusher-js@54bde39 they started using sockjs as a second fallback method.

As of now slanger works fine with WebSockets and with Flash. But if you've got a client which does not have WebSocket support and does not have Flash (for example my Android 4.0.4 smartphone), the pusher-js library tries to talk with the original pusher.com server (via http://sockjs.pusher.com/pusher)

Do you have plans to support sockjs too? Or should one use pusher-js <= v1.12.3

adharris commented Dec 3, 2013

I encountered this while restarting slanger; the client would connect fine, id restart the server with the client still connected, and the client would attempt to reconnect to pusher.

Using the current version of the client, I've worked around this by disabling the sockjs transport as a fallback:

pusher = new Pusher(key, {
    wsHost: "slanger host",
    wsPort: "slanger port",
    wssPort: "slanger port",
    disabledTransports: ['sockjs'],
});

This appears to work, though I +1 the notion of adding sockjs to slanger.

Owner

stevegraham commented Jul 18, 2014

I'll look into this.

Owner

stevegraham commented Dec 26, 2014

SockJS is being implemented in the next release.

@stevegraham stevegraham self-assigned this Dec 26, 2014

@stevegraham stevegraham added this to the Rewrite milestone Dec 29, 2014

Any progress on this?
Thanks!!

Hengjie commented Feb 2, 2016

@stevegraham any progress on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment