Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tweaked websocket support at Heroku #9

Open
skyluc opened this issue Mar 26, 2014 · 0 comments
Open

Tweaked websocket support at Heroku #9

skyluc opened this issue Mar 26, 2014 · 0 comments

Comments

@skyluc
Copy link
Member

skyluc commented Mar 26, 2014

I received this change notification about the websocket support at Heroku. Having a quick look at the doc and the application, I don't really see anything new.

To be investigated.

WebSockets now supports Keep-Alive

As a means of improving the performance of applications using our WebSockets implementation, Heroku has updated the way that the platform's routing architecture handles HTTP Keep-Alive. With Keep-Alive now enabled at the routing tier, applications can expect robust and normalized performance for both WebSockets and regular HTTP traffic.

Enabling this was a non-trivial engineering effort, due to the interplay between our load balancers, routing mesh, and dyno fleets. The new routing system is now in a well-tested and stable state, and we are giving more applications access to the new and improved router.

Your application, scala-ide-dashboard, will be on the new WebSockets and Keep-Alive router as of 03.26.14.

The documentation for the updated router can be found here: https://devcenter.heroku.com/articles/heroku-labs-router.

If you have any feedback or concerns, please let us know at rand@heroku.com.

Thank you!

Rand Fitzpatrick
Heroku

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant