Status: Usable, but a work in progress. Feedback encouraged!
An open standard describing a mix of client and server-side code designed to communicate over a persistent connection. This will usually be a WebSocket connection, but any Realtime Transport module is compatible.
Realtime Services are designed to be very easy to understand, write, test and share on
var service =console.log'Message in from server:' msg;setIntervalserverbroadcast'Hello!';1000;
(all alpha quality for now)
- client and server code can expose APIs to be called by the app
- easy to write tests
- the realtime-service-client can run in a browser or separate node process
- each service has it's own directory to store files (e.g. model definitions)
- efficiently handles callbacks, even for non-JSON messages
- services can optionally use Sessions (provided by the server)
- server is notified when a client connect/disconnect (allowing cleanup)
- optionally handles JSON encoding/decoding for you
- provides a standard logging API
- ultra light weight client-side code (for sending to browser)
Realtime Services do not care about:
- the underlying transport layer (abstracted away by Realtime Transport)
- how code is delivered to the browser (left to the framework or app to implement)
Realtime Services are currently implemented in Prism, the realtime server component of SocketStream 0.4.
As other frameworks / toolkits implement them, they will be listed here.
Realtime Services consist of
- This - the server-side library
- The realtime-service-client module
- The Realtime Server Spec (Coming soon!)
Realtime Services are the evolution of an idea called "Request Responders" which first appeared in SocketStream 0.3. Despite a horribly clunky API, the idea proved to be popular with third-party modules for Backbone and Angular soon appearing.
Realtime Services will be one of the key features of SocketStream 0.4. However, I hope by ensuring the spec is a simple as possible (with minimal dependencies), other frameworks will support Realtime Services in the future. The ultimate goal is an ecosystem of reusable components using 100% standard