Re:Deprecate GraphQL Subscriptions over WebSockets in Favour...
by jensneuse on Saturday September 26, 2020 @01:00PM
(#24600295)
If your website is HTTP/2 all the way, do you really want to add WebSockets which force the browser to initiate another TCP connection? The EventSource or Streams API can easily replace WebSockets for most use cases.
Re:Deprecate GraphQL Subscriptions over WebSockets in Favour...
by pornel on Saturday September 26, 2020 @02:13PM
(#24600875)
On the Web nothing really dies. However, WebSockets are from the HTTP/1 era. They were PITA to support even in HTTP/1 servers, and they're even more annoying in HTTP/2 deployments.
This is the first sentence, and I’m dubious - not about the lack of HTTP/2 but that WebSockets are dead, because I’ve never heard this until now. Is this really the case?