You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Lovely project! I myself got interested in this idea and made a few POCs in haskell and rust, although I decided to do some kind of "in-band control" to avoid having arbitrary large notify payloads (there is a limit after all, and it wasn't meant for passing large json payloads).
Anyway, my question really was about using websockets, a (pretty much) obsolete protocol for the age of HTTP/2 or 3.
It forces Connection upgrades, which plays badly with proxies, cannot exploit HTTP/2 streams, and this is not exploiting the bi-directional features, since this tool is purely from server to clients (i.e Server-sent).
That's why I wonder why you didn't use Server-Sent events?
Thanks for reading :)
The text was updated successfully, but these errors were encountered:
Hi! Lovely project! I myself got interested in this idea and made a few POCs in haskell and rust, although I decided to do some kind of "in-band control" to avoid having arbitrary large notify payloads (there is a limit after all, and it wasn't meant for passing large json payloads).
Anyway, my question really was about using websockets, a (pretty much) obsolete protocol for the age of HTTP/2 or 3.
It forces Connection upgrades, which plays badly with proxies, cannot exploit HTTP/2 streams, and this is not exploiting the bi-directional features, since this tool is purely from server to clients (i.e Server-sent).
That's why I wonder why you didn't use Server-Sent events?
Thanks for reading :)
The text was updated successfully, but these errors were encountered: