More Related Content

Slideshows for you(20)

Let's Get Real (time): Server-Sent Events, WebSockets and WebRTC for the soul

  1. Let’s get real (time): Server-Sent Events,WebSockets and WebRTC for the soul A guided tour of modern browser networking Swanand Pagnis swanand@pagnis.in
  2. Yours truly • Originally from Krypton, often mistaken as the last survivor • Sent to earth in a spaceship while still a baby • A few useful superpowers • Suspiciously good at hiding in plain sight
  3. Yours truly • Originally from Krypton, often mistaken as the last survivor • Sent to earth in a spaceship while still a baby • A few useful superpowers • Suspiciously good at hiding in plain sight
  4. Yours truly • Bangalore RUG, Mysore RUG, Garden City RubyConf • Hack code at Simplero for a living • Twitter @_swanand • Github @swanandp
  5. What’s in store for us
  6. 1. Why bother ? What’s in store for us
  7. 1. Why bother ? 2. The Zen of RealTime Communication What’s in store for us
  8. 1. Why bother ? 2. The Zen of RealTime Communication 3. Concepts and app Integration with: What’s in store for us
  9. 1. Why bother ? 2. The Zen of RealTime Communication 3. Concepts and app Integration with: 1. SSE What’s in store for us
  10. 1. Why bother ? 2. The Zen of RealTime Communication 3. Concepts and app Integration with: 1. SSE 2. WebSockets What’s in store for us
  11. 1. Why bother ? 2. The Zen of RealTime Communication 3. Concepts and app Integration with: 1. SSE 2. WebSockets 3. WebRTC What’s in store for us
  12. 1. Why bother ? 2. The Zen of RealTime Communication 3. Concepts and app Integration with: 1. SSE 2. WebSockets 3. WebRTC 4. Further reading and open source opportunities What’s in store for us
  13. Problems with traditional approaches Why Bother ?
  14. 1. Poor performance because of high latency 2. Neither truly async nor truly real time, often limited toText transfer only 3. Either additional complexity and inconvenience or hacky methods