The WHATWG Web Applications 1.0 proposal included a mechanism to push content to the client. On September 1, 2006, the Opera web browser implemented this new experimental technology in a feature called "Server-Sent Events".
|Mozilla Firefox||Yes||Starting with Firefox 6.0 |
|Opera||Yes||Starting with Opera 11 |
|Safari||Yes||Starting with Safari 5.0 |
- TRVSEventSource - Server-sent events EventSource implementation in ObjC for iOS and OS X using NSURLSession.
- Cramp - Ruby/EventMachine based server implementation for WebSocket and Server-Sent Events.
- django-sse - HTML5 Server-Sent Events integration for Python/Django.
- flask-sse - A simple Flask extension for HTML5 server-sent events support, powered by Redis.
- sse - Server Sent Events protocol implementation on python2 and python3 in the same codebase.
- event-source-library - Server Sent Events protocol implementation in python2 with tornado. Client and server implementations.
- SignalR - Transparent implementation for ASP.NET.
- Mojolicious - Perl real-time web framework.
- Hoa\Eventsource - PHP Server-Sent Events implementation.
- sse-stream - Node.js/Browserify Server-Sent Events implementation (client and server).
- partial.js - partial.js is node.js web application framework - supports Server-Sent Events, WebSockets (RFC 6455) and multipart/x-mixed-replace.
- HTML5 server-sent events W3C draft specification.
- HTML5 Server-push Technologies, Part 1. Introduction into HTML5 Server-push Technologies. Part 1 covers ServerSent Events.
- Using server-sent events. Concise example how to use server-sent events, on the Mozilla Developer Network.
- Django push: Using Server-Sent Events and WebSocket with Django Django push: Using Server-Sent Events and WebSocket with Django.