Closed clone1018 closed 4 years ago
Could also use SSE for this. Pretty much just fling data at a url and have the client read and handle it. No need for keeping a connection up or using any standards other than HTTP.
SSE is worth considering but there are a couple notable limitations:
Services would have to make separate requests to send data back to Glimesh, which can be a little extra hurdle and a source of latency if bots or services want to respond quickly to events they're listening for.
Apparently there's a pretty strict connection limit with the EventSource API in Chromium and Firefox as well, which was marked won't fix.
I lean mostly toward web sockets as they seem to be the 'de facto' standard for real-time web APIs - they've been embraced by a lot of services and are familiar to many of the developers working in this space.
Some initial work completed on this, next up is to add subscriptions.
Added in this PR: https://github.com/Glimesh/glimesh.tv/pull/173
Current unusable until we get cross_origin disabled in Phoenix.
Usable since https://github.com/Glimesh/glimesh.tv/pull/184
Should include: