The SSE Server Hub allows for HTTP Client Requests (through a Rest Expose API) to be persisted for Event Streaming as per protocol1. This is accomplished by switching the mime-type response to the appropriate text/event-stream and flushing the messages complying to the event source format2.
The SSE Client implements the Event Source JS Interface containing the Server Sent Event API, also per protocol3.
Effectively, no third parties are required for Server Push/Messaging.
*NOTE*
Please refer to the Documentation tab for further details.
1 https://html.spec.whatwg.org/multipage/server-sent-events.html
2 https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events
3 https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events
- Fixed duplicating eventsource initializer when calling ajax submits on blocks containing the SSE. The traditional SSE client now cleans up the previous instance of SSE on that particular block by assigning a unique ID(provided by the SSE block itself)
- Added a visual cue on design time to better know that SSE is being used on a particular screen/block