Server-Sent Events

Mobile Web

Dependencies

  • Tizen 2.4 and Higher for Mobile

Content

Related Info

The Server-Sent Events feature is used to implement server push functionality in a Web environment. The server push feature has evolved over time from a hidden IFrame through Ajax polling and Comet to the current implementation of server-sent events.

This feature is supported in mobile applications only.

The Server-Sent Events API defines a simple data structure and interface, and a communication mechanism to realize the server push. In addition, it can handle the received data in the general DOM event format. However, the API repeatedly requests the data from the client to the server, so it is not a complete server push.

The repeat period of the server request is determined by the retry field value of the event stream data. If the value is not defined, the repeat period is the default value of the browser.

The main features of the Server-Sent Events API include:

  • Creating an EventSource instance

    The EventSource interface is the core object of server-sent event implementation. Creating a new EventSource instance triggers repeated server request automatically, and allows you to use the receiving data event. When creating the EventSource instance, you must use the URL of the server page sending the event stream as a parameter.

  • Receiving server push data

    After triggering the server requests, you can receive push data from the server by implementing the message event.

    The received event stream data is parsed as a MessageEvent object, to make the target data easily accessible.

Triggering Server Push Requests

To take advantage of the server push feature, you must learn to connect to the server to request push data:

  1. Create an EventSource interface instance:

    <script>
        var serverPage = 'http://165.213.198.151:8080/server_sent_events_server.php';
        var eventSource = new EventSource(serverPage);
    
    NoteFor the server push to work, the serverPage parameter must contain the actual push server URL.
  2. Implement the event handler for the open event:
        var log = document.getElementById('log')
    
        /* Open event */
        eventSource.onopen = function(e) {
            log.innerHTML += '<p>open: ' + new Date() + '</p>';
        };
    </script>
    

    The open event is triggered repeatedly based on the retry value of the event stream data format, to request push messages from the server.

In the following figure, the open event is fired every 2 seconds.

Figure: Push request event

Push request event

Source Code

For the complete source code related to this use case, see the following files:

Receiving Server Push Data

To take advantage of the server push feature, you must learn to handle the push data events:

  1. Define the data server that the client connects to, according to the event stream interpretation rules.

    Set the MIME type to text/event-stream so that the event stream can be sent, and set the header not to be cached.

    <?php
       header('Content-Type: text/event-stream');
       header('Cache-Control: no-cache');
    
       echo "retry: 2000\n\n"; /* Reconnection interval */
       echo "data: push time => ". date('r') . "\n\n";
    
       flush();
    ?>
    
  2. Create an EventSource interface instance and implement the event handler for the message event:

    <script>
        var serverPage = 'http://localhost/server_sent_events_server.php';
        var eventSource = new EventSource(serverPage);
        var log = document.getElementById('log');
    
        /* Open event */
        eventSource.onopen = function(e) {
            log.innerHTML += '<p>-----------------------</p>';
            log.innerHTML += '<p>open: ' + new Date() + '</p>';
        };
    
        /* message event */
        eventSource.onmessage = function(e) {
            log.innerHTML += '<p>[push data]: <br/>' + e.data + '</p>';
        };
    </script>
    

In the following figure, the open event is fired every 2 seconds and the message event shows that push data is received.

Figure: Push message event

Push message event

Source Code

For the complete source code related to this use case, see the following files: