Live Streaming & Server Sent Events

Live Streaming
&
Server Sent Events
Tomáš Kramár
@tkramar

When?
● Server needs to stream data to client
– Server decides when and what to send
– Client waits and listens
– Client does not need to send messages
– Uni-directional communication
– Asynchronously

How? / Terminology
● AJAX polling
● Comet
● WebSockets
● Server-Sent Events

AJAX polling
Any news?

Browser/Client Server

AJAX polling
Any news?

No


AJAX polling
Any news?

No

Any news?

No


AJAX polling
Any news?

No

Any news?

No

Any news?

Browser/Client Yes! Server

AJAX polling
Any news?

No

Any news?

No

Any news?

Browser/Client Yes! Server

Any news?

No

AJAX polling
● Overhead
– Establishing new connections, TCP handshakes
– Sending HTTP headers
– Multiply by number of clients
● Not really realtime
– Poll each 2 seconds

Comet
● set of technology principles/communication
patterns
● mostly hacks
– forever-iframe
– htmlfile ActiveX object
– XHR multipart/streaming/long-polling
– Flash
– ..

WebSockets
● bi-directional, full-duplex communication
channels over a single TCP connection
● HTML5
● being standardized

Server-Sent Events
● HTML5
● Traditional HTTP
– No special protocol or server implementation
● Browser establishes single connection and
waits
● Server generates events

SSE
Request w parameters

id: 1
event: display
data: { foo: 'moo' }


SSE
Request w parameters

id: 1
event: display
data: { foo: 'moo' }

Browser/Client id: 2 Server
event: redraw
data: { boo: 'hoo' }

Case study
● Live search in trademark databases
● query
– search in register #1
● Search (~15s), parse search result list, fetch each result
(~3s each), go to next page in search result list (~10s),
fetch each result, ...
– search in register #2
● ...
– …
● Don't let the user wait, display results when
they are available

Client

this.source = new EventSource('marks/search');

self.source.addEventListener('results', function(e) {
self.marks.appendMarks($.parseJSON(e.data));
});

self.source.addEventListener('failure', function(e) {
self.errors.showError();
});

self.source.addEventListener('status', function(e) {
self.paging.update($.parseJSON(e.data));
});

Client gotchas
● Special events:
– open
– error
● Don't forget to close the request

self.source.addEventListener('finished', function(e) {
self.status.searchFinished();
self.source.close();
});

Server
● Must support
– long-running request
– Live-streaming (i.e., no output buffering)
● Rainbows!, Puma or Thin
● Rails 4 (beta) supports live streaming

Rails 4 Live Streaming
class MarksController < ApplicationController
include ActionController::Live
def results
response.headers['Content-Type'] = 'text/event-stream'
sse = SSE.new(response.stream)
Tort.search(params[:query]) do |on|
on.results do |hits|
sse.write(hits, event: 'result')
end
on.status_change do |status|
sse.write(status, event: 'status')
end
on.error do
sse.write({}, event: 'failure')
end
end
end
end

require 'json'

class SSE
def initialize io
event: displayn
@io = io data: { foo: 'moo' }nn
end

def write object, options = {}
options.each do |k,v|
@io.write "#{k}: #{v}n"
end
@io.write "data: #{JSON.dump(object)}nn"
end

def close
@io.close
end
end

Timeouts, lost connections, internet
explorers and other bad things
● EventSource request can be interrupted
● EventSource will reconnect automatically
● What happens with the data during the time
connection was not available?

Handling reconnections
● When EventSource reconnects, we need to
continue sending the data from the point the
connection was lost
– Do the work in the background and store events
somewhere
– In the controller, load events from the storage
● EventSource sends Last-Event-Id in HTTP
header
– But we don't need it if we remove the processed
events

marks/search?q=eset GirlFriday
Search
3342345
HTTP 202 Accepted
marks/results?job_id=3342345

Browser Server Redis

marks/results?job_id=3342345

MarksController

event: results
data: {foo: 'boo'}

event: status
data: {moo: 'hoo'}


def search!
uuid = UUID.new.generate(:compact)
TORT_QUEUE << { phrase: params[:q], job_id: uuid }

render status: 202, text: marks_results_path(job: uuid)
end

def results
queue = SafeQueue.new(Channel.for_job(params[:job]), Tmzone.redis)
finished = false

begin
begin
queue.next_message do |json_message|
message = JSON.parse(json_message)
case message["type"]
when "results" then
sse.write(message["data"], event: 'results')
when "failure" then
when "fatal" then
sse.write({}, event: 'fatal')
finished = true
when "status" then
sse.write(message["data"], event: 'status')
when "finished" then
sse.write({}, event: 'finished')
finished = true
end
end
end while !finished
rescue IOError
# when clients disconnects
ensure
sse.close
end
end
end


def search!
generate job_id

end

def results
finished = false

begin
begin
when "results" then
when "failure" then
when "fatal" then
finished = true
when "status" then
finished = true
end
end
end while !finished
rescue IOError
ensure
sse.close
end
end
end


def search!
start async job (GirlFriday)
end

def results
finished = false

begin
begin
when "results" then
when "failure" then
when "fatal" then
finished = true
when "status" then
finished = true
end
end
end while !finished
rescue IOError
ensure
sse.close
end
end
end


def search!

end
send results URL

def results
finished = false

begin
begin
when "results" then
when "failure" then
when "fatal" then
finished = true
when "status" then
finished = true
end
end
end while !finished
rescue IOError
ensure
sse.close
end
end
end


def search!

end

def results
queue = SafeQueue.new(Channel.for_job(params[:job]), Tmzone.redis) Get queue for this job,
finished = false async job is pushing
begin
to this queue
begin
when "results" then
when "failure" then
when "fatal" then
finished = true
when "status" then
finished = true
end
end
end while !finished
rescue IOError
ensure
sse.close
end
end
end


def search!

end

def results
finished = false

begin
begin
Fetch next message
message = JSON.parse(json_message) from queue (blocks until
when "results" then one is available)
when "failure" then
when "fatal" then
finished = true
when "status" then
finished = true
end
end
end while !finished
rescue IOError
ensure
sse.close
end
end
end


def search!

end

def results
finished = false

begin
begin
when "results" then
when "failure" then
when "fatal" then
finished = true
when "status" then
finished = true
end
end
end while !finished
rescue IOError
# when clients disconnects IOError is raised when client
ensure
sse.close disconnected and we are
end
end writing to response.stream
end

GirlFriday worker
class SearchWorker
def self.perform(phrase, job_id)
channel = Channel.for_job(job_id)
queue = SafeQueue.new(channel, Tmzone.redis)

Tort.search(phrase) do |on|
on.results do |hits|
queue.push({ type: "results", data: hits }.to_json)
end
on.status_change do |status|
queue.push({ type: "status", data: status }.to_json)
end
on.error do
queue.push({ type: 'failure' }.to_json)
end
end
queue.push({ type: "finished" }.to_json)
end
end

SafeQueue
class SafeQueue
def initialize(channel, redis)
@channel = channel
@redis = redis
end

def next_message(&block)
begin
_, message = @redis.blpop(@channel)
block.call(message)
rescue => error
@redis.lpush(@channel, message)
raise error
end
end

def push(message)
@redis.rpush(@channel, message)
end
end

EventSource Compatibility
● Firefox 6+, Chrome 6+, Safari 5+, Opera 11+,
iOS Safari 4+, Blackberry, Opera Mobile,
Chrome for Android, Firefox for Android

Fallback
● Polyfills
– https://github.com/remy/polyfills/blob/master/Event
Source.js
● Hanging GET, waits until the request terminates,
essentially buffering the live output
– https://github.com/Yaffle/EventSource
● send a keep-alive message each 15 seconds

Summary
● Unidirectional server-to-client communication
● Single request
● Real-time
● Easy to implement
● Well supported except for IE

Live Streaming & Server Sent Events

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Live Streaming & Server Sent Events

Ähnlich wie Live Streaming & Server Sent Events (20)

Mehr von tkramar

Mehr von tkramar (8)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Live Streaming & Server Sent Events