3 ms·
60s heartbeat interval, job done. We've got multiple internal apps using WebSockets in production, for years. I have to say I don't really get all the concern
by philipwhiuk 2y ago
60s heartbeat interval, job done.
We've got multiple internal apps using WebSockets in production, for years. I have to say I don't really get all the concern in the article about upgrading the connection - any decent backend framework should handle this for you without a problem.
Hacker News articles on new libraries generally live in the 1% of the 1%. For lots of websites, they don't need a web-socket because they are just doing CRUD. For the 1% doing live updates, web-sockets are great and straight-forward. For whatever specialised use case the article has, sure there's something even less well supported you can pivot to.
- bonestamp2 2y agoWe use a much short heartbeat interval because our use case is for real time control and monitoring so our users need to know immediately if the connection is lost.