jQuery SSE

A lightweigth jQuery Plugin for Server-Sent Events (SSE) EventSource Polyfill. This plugin try to use the native EventSource object if it supported by the browser. If there is no native support the request is made by ajax requests (polling). You do not need to change the server side nor the client side.

If you are looking for a SSE Polyfill library without jQuery dependency try yaj-sse. The yaj-sse is a port from version 0.1.4 of jQuery SSE.

Example

Client Side

1var sse = $.SSE('http://example.com/sse-server.php', {
2    onMessage: function(e){ 
3        console.log("Message"); console.log(e); 
4    }
5});
6sse.start();

Server Side

1echo "data: My Message\n";
2echo "\n";

Dependencies

• jQuery

Install

Just download the repository and point to the jQuery plugin:

1<script src="jquery.sse.js" ></script>

or

1<script src="jquery.sse.min.js" ></script>

You can also install using bower:

1bower install jquery-sse

Usage:

Constructor

var sse = $.SSE(url, settings);

• url: URL for the server will be sent the events to this page;
• settings: The events and options for the SSE instance

Settings List

All the options:

var sseObject = $.SSE('sse-server.php', {
    onOpen: function (e) {},
    onEnd: function (e) {},
    onError: function (e) {},
    onMessage: function (e) {},
    options: {},
    headers: {},
    events: {}
});

Event onOpen

Fired when the connection is opened the first time;

1onOpen: function(e){ 
2    console.log("Open"); console.log(e); 
3},

Event onEnd

Fired when the connection is closed and the client will not listen for the server events;

1onEnd: function(e){ 
2    console.log("End"); console.log(e); 
3},

Event onError

Fired when the connection error occurs;

1onError: function(e){ 
2    console.log("Could not connect"); 
3},

Event onMessage

Fired when the a message without event is received

1onMessage: function(e){ 
2    console.log("Message"); console.log(e); 
3},

Custom Options

Define the options for the SSE instance

1options: {
2    forceAjax: false
3},

• forceAjax: Uses ajax even if the EventSource object is supported natively;

Custom Events

Fired when the server set the event and match with the key

For example, if you have a custom event called myEvent you may use the follow code:

1events: {
2    myEvent: function(e) {
3        console.log('Custom Event');
4        console.log(e);
5    }
6}

Server side:

1echo "event: myEvent\n";   // Must match with events in the HTML.
2echo "data: My Message\n";
3echo "\n";

Custom Headers

You can send custom headers to the request.

1headers: {
2    'Authorization': 'Bearer 1a234fd4983d'
3}

Note: As the EventSource does not support send custom headers to the request, the object will fallback automatically to 'forceAjax=true', even this it is not set.

Methods

start

Start the EventSource communication

1sse.start();

stop

Stop the EventSource communication

1sse.stop();

Quirks

The ajax does not support the streaming as the event source supports. In that case we recommend create a server without streaming and set the "retry" to determine query frequency;

Example Server Side:

1echo "retry: 3000\n";
2echo "data: My Message\n";
3echo "\n";

Minify

apt install uglifyjs

uglifyjs --compress 'drop_console,drop_debugger' --mangle -r '$,require,exports,_' -o jquery.sse.min.js jquery.sse.js

Running the examples

Start the webserver:

1docker run -it --rm -p 8080:80 -v $PWD:/var/www/html byjg/php:7.4-fpm-nginx 

Open the browser: http://localhost:8080/examples/sse-client.html

References

• http://www.w3.org/TR/2009/WD-eventsource-20091029/
• https://developer.mozilla.org/en-US/docs/Server-sent_events/Using_server-sent_events
• http://html5doctor.com/server-sent-events/
• http://www.html5rocks.com/en/tutorials/eventsource/basics/

---

Open source ByJG