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…

Dec 13, 2016 · 7:45 PM UTC

3
3
15
Replying to @stilkov
http2 won't replace websockets, each has its place.
1
I agree each has its place, which is why I object to the clickbait title and unnecessary bashing of HTTP in that post
1
1
Replying to @stilkov
why? Because you disagree with the explanation that follows?
1
Replying to @stilkov
it would be very interesting to see how badly they damaged their results with this wrong assumption.