Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Reject.js: The Future is Realtime

miksago
October 12, 2011

Reject.js: The Future is Realtime

Prefix: This is actually the first time I gave the talk, and it was with about 36 hours notice, I started without slides and got to here by the time I gave the talk.

Over the last decade, we've seen a massive shift in the way that the web works. This talk aims to introduce the realtime web, show why it can be really important.

miksago

October 12, 2011
Tweet

More Decks by miksago

Other Decks in Programming

Transcript

  1. • Overview of the past • The realtime shift •

    Future thinking Wednesday, 12 October 2011
  2. • Overview of the past • The realtime shift •

    Future thinking Wednesday, 12 October 2011
  3. • Early web • PHP / LAMP Stack • MVC

    / Social Web Overview of the past Wednesday, 12 October 2011 To paraphrase Mikeal Roger’s recent blog post, which came out just after I’d submitted my talk proposal on monday: - Early web: everything static, edited by hand / desktop software, - PHP / Simplistic Stack: some user interaction with content, some database access, etc - MVC / Social Web: massive shift towards user generated content, loads of database access, the take off of AJAX, etc.
  4. • Overview of the past • A Shift to Realtime

    • Future thinking Wednesday, 12 October 2011
  5. A shift to Realtime • The web has become more

    interactive • Users expect things to be “now” • And why should they have to wait? Wednesday, 12 October 2011
  6. • We researched page-load time • We used AJAX to

    decrease wait-time on interactions • We then tried to simulate “realtime” with AJAX and related technologies A shift to Realtime Wednesday, 12 October 2011
  7. The Tried Simulations • HTTP Polling • LiveConnect • Forever

    iFrame • XHR Long-polling • XHR Streaming Wednesday, 12 October 2011 - I don’t know too much about these.
  8. The realtime shift • HTML5 Introduces many new API’s •

    One of those is WebSockets, which addresses the need for low-latency bi-directional communication Wednesday, 12 October 2011