Under the headings, the deck is a definition that turns into a design. SocketStream is "a modular Node.js web framework for building fast, responsive single-page realtime apps" — not a realtime add-on bolted onto an HTTP app, but a framework whose transport is the application. The talk walks that through in 8 top-level sections (24 slides in total).

Concretely, a 2012 app would open one socket — Socket.IO in 0.3, SockJS as a modular alternative — and hang the app off it. ss.rpc('board.current', callback) calls a server action by name and answers asynchronously; ss.publish.all('newUser', user) pushes to every connected client; req.session.channel.subscribe('boardUpdates') scopes those pushes to a channel. The route handler never renders HTML — res.serveClient('main') ships a named client, which ss.client.define('main', …) composed from a view, CSS, libs/jquery.min.js, app code and templates.

The unusual bet is the module system. window.ss = require('socketstream') and exports.actions run the same CommonJS require/exports idiom on client and server, years before Browserify or Webpack made that ordinary, so the two sides can share code. Sessions cross the wire too: once an RPC action adds req.use('session'), the same req.session — including session.facebook set during the initial HTTP handshake — is visible inside socket calls.

Nothing in the examples is hypothetical: every snippet is captioned "code examples based on our app". That app is a board: clients call board.current, subscribe to boardUpdates, upload through fileupload.html and userdetails.html, authenticate via a facebookAuth.js middleware, and download a zipped set of images per version through a custom zipStream.js — the screen shown on the Demo slide, where the terminal reads SockJS v0.3.1 bound to "/ws" and a Console Server running on port 5000.