On Sun, Sep 25, 2016 at 10:02 AM, Merlijn van Deen (valhallasw) < valhallasw@arctus.nl> wrote:
You could consider not implementing streaming /at all/, and just ask clients to poll an http endpoint, which is much easier to implement client-side than anything streaming (especially when it comes to handling disconnects).
On the other hand, polling requires repeated TCP handshakes, repeated HTTP headers sent and received, all that work done even when there aren't any new events, non-real-time reception of events (i.e. you only get events when you poll), and decision on what acceptable minimum values for the polling interval are.
And chances are that clients that want to do polling are already doing it with the action API. ;) Although I don't know what events are planned to be made available from this new service to be able to say whether they're all already available via the action API.