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
of response buffering ( Remember our first Zen ? ) 2. Evented architecture works in our favour ( Think of EM::Deferrable or Thin ) 3. Long running connection means long running process on the server Server-Sent Events : App Integration
> 4.0 ) 2. You keep the full context ( current_user etc ) 3. Integration friendly, almost a drop-in feature into existing Rails apps ActionController::Live
and your server and client act as clients to this server 2. Pub / sub model, drop-in integration with your app 3. Graceful degradation 4. No app context Faye + Your App
Use a separate process / service / app for the real time part ( e.g. Faye or Pusher or BYOT ) 2. Use existing infrastructure for non real time aspects of the app Recommended approach Rant
far • Open source all your throw-away code written during learning ( Mine is on Github ) • Async-proof versions of commonly needed ruby gems ( e.g. github.com/rkh/async-rack )
simple board games • To write calendar based real time apps • Augment the testing libraries to test real time stuff • Write and make your benchmarks available