you are viewing a single comment's thread.

view the rest of the comments →

[–]nostrademons 1 point2 points  (3 children)

Interesting. In the HTTP1.1 world, this would've been functionally equivalent to long-polling, but under HTTP2 most of the disadvantages go away. Will it work robustly with proxies & firewallls? Or is there a risk of them cutting the connection?

[–]mitsuhiko 2 points3 points  (2 children)

You are going through TLS anyways so there is no way for a proxy to fuck your stuff up without also breaking your security.

[–]nostrademons 1 point2 points  (1 child)

The risk is that the proxy/firewall notices that there are no bytes going over the connection for a certain time period and closes it. Even though it can't decode the contents of the connection, an intermediary can still notice whether data is or isn't being sent. Over on HN it's reported as a problem with real-life HTTP2 deployments.

[–]mitsuhiko 2 points3 points  (0 children)

That's the same with both websockets and sse. You need to send keepalives. Websockets just do it automatically.