SSE are asynchronous, but unidirectional. Whereas websockets are asynchronous and
bidirectional.
Enabling push through SSE, clients could use a combination of request/response for the
main communication (i.e. execution of operations, reading the model contents, etc) and SSE
for the notifications .
Using websockets we could move all client communication to one paradigm. But do we need
it?
Currently have cases where clients keep polling for system state changes (i.e. server
restart, deployments, etc). Typically the things that take some time to complete. So I am
wondering if these cases could benefit from an asynchronous bidirectional communication
channel. But I guess this depends on how the DC processes management operations and if
asynchronous responses would fit into the picture.
/Heiko
On Feb 26, 2013, at 6:37 PM, David M. Lloyd <david.lloyd(a)redhat.com> wrote:
I don't know, it seems like overkill. I think
http://html5doctor.com/server-sent-events/ is probably a better option
than web sockets or polling as it is supported in the browser with a
simple API and doesn't require a lot of complex server-side support.