Server-sent events

From Wikipedia, the free encyclopedia

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 HTML5[1] by the WHATWG. The media type for SSE is text/event-stream.


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

Browser support[edit]

All modern browsers support server-sent events: Firefox 6+, Google Chrome 6+, Opera 11.5+, Safari 5+, Microsoft Edge 79+.[5]



  • Service Stack EventSource library with both server and client implementations.


  • SignalR - Transparent implementation for ASP.NET.


  • HaSSEs Asynchronous server-side SSE daemon written in C (It uses one thread for all connected clients).


  • Lasse EventSource server handler for Erlang's cowboy
  • Shotgun EventSource client in Erlang


  • eventsource EventSource library for Go.
  • go-sse SSE implementation for Go.
  • sse SSE with optimized decoder for Go
  • gosse Server-sided implementation with channel concept and further features for out-of-the-box use.
  • sse Server Sent Events server and client for Golang
  • tmaxmax/go-sse Fully featured, spec-compliant HTML5 server-sent events library


  • Javalin - lightweight Java and Kotlin web framework
  • jEaSSE - Server-side asynchronous implementation for Java servlets and Vert.x
  • Akka HTTP has SSE support since version 10.0.8
  • alpakka Event Source Connector EventSource library for alpakka which supports reconnection
  • Spring WebFlux Server and client side Java implementation built on reactive streams and non-blocking servers
  • Jersey has a full implementation of JAX-RS support for Server Sent Events as defined in JSR-370
  • Micronaut HTTP server supports emitting Server Sent Events
  • JeSSE - Server-side library with user/session management, group broadcast, and authentication
  • Armeria has server and client-side asynchronous SSE implementation built on top of Netty and Reactive Streams
  • Play Framework Event Source for server-sent event emission
  • SSE Client SSE Client library


Objective C[edit]

  • TRVSEventSource - EventSource implementation in Objective-C for iOS and macOS using NSURLSession.





  • Faye - Simple pub/sub messaging for the web.
  • Iodine - HTTP, WebSockets and EventSource (SSE) and Native Pub/Sub.


  • hyper A low-level HTTP library.
  • Warp A web server framework.



  • EventSource - EventSource implementation using NSURLSession.

See also[edit]


  1. ^ "HTML Living Standard: 9.2 Server-sent events". WHATWG. 31 March 2022.
  2. ^ "Web Applications 1.0 specification". WHATWG. 2006-09-01. Archived from the original on 2006-09-01. Retrieved 2006-09-01.{{cite web}}: CS1 maint: unfit URL (link)
  3. ^ Bersvendsen, Arve (1 September 2006). "Event Streaming to Web Browsers".
  4. ^ Stream Updates with Server-Sent Events, Eric Bidelman, HTML5Rocks website.
  5. ^ When can I use... Server-sent DOM events

External links[edit]