Pusher-js 2.0.0 released: WebSockets, comprehensive legacy support

blog.pusher.com

25 points·c-oreills··5 comments

From the comments, someone notes that GZIP isn't enabled. Someone Pusher replies: "We use Amazon Cloudfront as our CDN right now and achieving this isn't as easy as we'd like it to be. It is on our backlog."

As great as AWS and the Cloudfront/S3 combo is, it's maddening that the combo can't serve both gzip and non-gzip versions from the same url [1].

[1] http://stackoverflow.com/questions/5442011/serving-gzipped-c...

just looked at the client library and noticed they use SockJS, interesting.

Legacy support sounds great!

Does it mean it doesn't fall back on Flash?

"Pusher has always worked across a wide variety of devices via a Flash based fallback mechanism, and we haven’t replaced this option in the newer version. Since the Flash version uses the WebSocket endpoint, it gets all the low latency, low overhead advantages of WebSockets. The drawbacks with this approach are that it involves downloading extra files, Flash isn’t installed on every browser, and certain ports need to be open on the client’s network."

The preference is always to get some sort of websocket connection. If native websockets aren't present and flash is enabled, it'll try to create a websocket connection via flash first. It's only if that fails for some reason that it tries to connect via other means.

Reply on news.ycombinator.com