A brief introduction to real-time web with no code, a bit of history and a.. actually, wait, there's no DeLorean's here...
Micheil Smith / @miksago
Node.js Dublin / 28th June 2012
Ask a question:
• Show the improvement in ‘experience’
• Use examples: stock exchange, games,
Facebook and iOS push noti ications
• Just hammer the message into them
An interesting answer:
So, perhaps, the
question is not
...but rather, what is
First, a quick story
It begins with this...
The story of the
• Alexander Graham Bell & team
• Invented between 1874 and 1876
• Patent #174,465 issued 1876
• Prior works: Telegraph, Postal
1886: Over 150, 000
in the United States
changed how we
Now... back to the
How do you deﬁne
My deﬁnition: Real-
time same or greater
speed than by
Let’s talk about
Long-polling ...and.... ...and...
Firstly, Server-sent Events
• Push-messaging from Server to Client
• Very simple, text-based protocol
• A W3C Standard
• Wide-spread, uniform browser support
• Bidirectional messaging
• Complex, yet powerful binary protocol
• A W3C + IETF Standard
• Wide-spread browser support, but
varying incompatible historic versions
Thirdly? Well, let’s
forget about those...
Socket.IO, Faye, or
Even if your intentions are good, it can
• Di icult to scale & manage
• Shift in development patterns
• Known as being “risky”
• Cloud hosting providers aren’t
always up with support
Whoa! Rock 'n' Roll.
• Greatly enhances user engagement
• Enables richer, faster applications
• Backed by “big players”
• The “next big thing”?
If my calculations are
correct, when this
baby hits eighty-eight
miles an hour, you're
going to see some
Oh, by the way, I
work for State
And we’re hiring.
Thanks for listening!
Geekli.st / Github / Twitter / State