A lot depends on the volume - you need back pressure support for high volume events over the internet - and the built-in ping/pong of WS makes this straightforward. I think it is pretty hard to do back pressure if unidirectional as well (need side endpoints, etc.).
> On Oct 23, 2024, at 9:44 AM, 'Zane Attahri' via golang-nuts > <golang-nuts@googlegroups.com> wrote: > > Second this, and go ever further. > > If you don’t need bi-directional communication, SSE are almost always the > better choice. Simpler to implement, standard, and easier to consume by > non-browser clients. > >> On Oct 23, 2024, at 10:37 AM, Brian Hatfield <bmhatfi...@gmail.com> wrote: >> >> I don't think it's quite so binary. Websockets are a lot more complex, >> require more sophisticated endpoints and load balancing. SSE has fine >> browser support in 2024, minus the ability to set auth headers. I think for >> cases with unidirectional communication, SSE is a choice worth evaluating > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/2A0061EB-36AA-472E-8B9D-81BBD0F779E0%40attahri.com. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/01173482-0DA0-4901-AA91-53A8D4B3C995%40ix.netcom.com.
