I stopped reading at “for each HTTP request, a new TCP connection is established”
A scalable WebSocket server with pub/sub represents a good alternative to RESTful HTTP architecture highscalability.com/blog/201…
3
3
15
http2 won't replace websockets, each has its place.
1
Replying to @jevdemon
I agree each has its place, which is why I object to the clickbait title and unnecessary bashing of HTTP in that post

Dec 13, 2016 · 9:17 PM UTC

1
1
Replying to @stilkov
we agree on both.