Server-sent events

Server-Sent Events (SSE) is a server push technology enabling a client to receive automatic updates from a server via an HTTP connection, and describes how servers can initiate data transmission towards clients once an initial client connection has been established. They are commonly used to send message updates or continuous data streams to a browser client and designed to enhance native, cross-browser streaming through a JavaScript API called EventSource, through which a client requests a particular URL in order to receive an event stream. The EventSource API is standardized as part of HTML Living Standard ^[1] by the WHATWG. The media type for SSE is text/event-stream.

All modern browsers support server-sent events: Firefox 6+, Google Chrome 6+, Opera 11.5+, Safari 5+, Microsoft Edge 79+.^[2] Since SSE does not use either persistent connections nor chunked transfer encoding, HTTP/1.1 is not a technical requirement.

The SSE mechanism was first specified by Ian Hickson as part of the "WHATWG Web Applications 1.0" proposal starting in 2004.^[3] In September 2006, the Opera web browser implemented the experimental technology in a feature called "Server-Sent Events".^{[4] [5]}

varsource=newEventSource('updates.cgi');
source.onmessage=function(event){
alert(event.data);
};

• Chunked transfer encoding
• Push technology
• Comet

• Server-Sent Events. HTML Living Standard.
• HTML5 Server-push Technologies, Part 1. Introduction into HTML5 Server-push Technologies. Part 1 covers ServerSent Events.
• Using Server-Sent Events. A concise example of how to use server-sent events, on the Mozilla Developer Network.
• EventSource reference on MDN
• Django push: Using Server-Sent Events and WebSocket with Django Django push: Using Server-Sent Events and WebSocket with Django.
• Server-Sent Events vs WebSockets

• HTML5
• Internet terminology
• Push technology
• Web development
• Internet stubs

• Articles with short description
• Short description is different from Wikidata
• All stub articles