29 ms·
I've used HTTP/2 SSE for TinyDev (docs.tinydevcrm.com) and I've encountered the need for a reverse proxy and the unidirectional dataflow to be kinda eh, even if
by yingw787 6y ago
I've used HTTP/2 SSE for TinyDev (docs.tinydevcrm.com) and I've encountered the need for a reverse proxy and the unidirectional dataflow to be kinda eh, even if it is great in theory. I haven't played around too much with WebSockets though, but IMHO money + traction carries a good deal of weight.
- tschellenbach 6y agoIsn't HTTP/2 SSE being deprecated?
- anderspitman 6y agoI sure hope not. Are you thinking of HTTP/2 server push?
- iomcr 6y agohttps://stackoverflow.com/questions/28582935/does-http-2-make-websockets-obsolete https://stackoverflow.com/questions/28582935/does-http-2-mak...
- jamescun 6y agoI've seen nothing to suggest SSE would be (or is even capable of being) deprecated on HTTP/2. You may be confusing it with HTTP/2 Push, where a server can inform a client of a future resource it will need, which is _de facto_ dead, with only a few real implementations beyond the bare minimum required by the HTTP/2 specification.
- anderspitman 6y agoWhy do you require a reverse proxy, and are those requirements unique to SSE for some reason? I guess I'm not seeing what the alternative setup would be, even with WebSockets.