With the addition of Websockets, other people's updates to a project backlog are pushed to everyone else viewing it. In this way Pusher is an incremental improvement, TrueStory didn't rely on these real time updates, they just improved the user experience in much the same way both CSS and JavaScript should enhance the user experience of a plain html page.
Existing Architecture
The bulk of the application code in TrueStory is on the client side, and relies on libraries …
- Luke Redpath: Pushing events to your iPhone using WebSockets and Pusher
- Ruby Inside: Pusher: WebSocket-powered Realtime Browser Push Service for Rubyists
- has_many :bugs, :through => :rails - Home: Introducing Cramp
- Ruby on Rails Podcast: Err Free - Ruby on Rails Podcast
- Kernow Soul Blog: Introducing Scupper, the JavaScript library for easily dealing with HTML snippets in test suites
- SD Ruby Podcast: Episode 065: HotRuby + jQuery: Ruby in the Browser
…handle talking directly to slow clients and high-latency apps ( Comet/ WebSockets) without nginx in front.
What is a "low-latency, high-bandwidth connection"?
Anything on localhost or the local area network that doesn't make the server sit idle, unable to service other requests.
Debugging
Can you give me an example of how to debug?
Reproducibility is critical to debugging. Processes are inherently simpler, as the process state is always well-defined on a per-request …
- A Fresh Cup: Double Shot #556
- Diego Carrion: Summary of new features in Inploy
- elc technologies - Blog : Ruby on Rails, iPhone, Flash, Agile, Interactive Design: Ruby Daemons and Angels
- Labnotes: Fuck Yeah fork(2)!
- Ryan Tomayko: I like Unicorn because it's Unix
- oldmoe: The Ruby 19x Web Servers Booklet
…connection to a server, and have immediate feedback when there are events they need to be notified of. Websockets make your applications more dynamic, and break them out of the traditional stateless request-response cycle. Your applications can therefore rely on maintained state in the browser which will be kept fresh with messages from your server.
Pusher makes adding Websockets to your application a quick and easy process. Pusher provides a simple Ruby gem ) for interacting with …
- has_many :bugs, :through => :rails - Home: Websockets made easy with Cramp
- igvita.com: Ruby & WebSockets: TCP for the Browser
- Bamboo Blog: Brain Dump of Real Time Web(RTW) and WebSocket
- paperplanes: A Collection Of Redis Use Cases
- Luke Redpath: Pushing events to your iPhone using WebSockets and Pusher
- Joe Fiorini: HTML5 Video on the iPhone
…atomicity and speed make it an excellent tool when tracking things directly from the web, e.g. through WebSockets or Comet. If you can use it asynchronously, all the better.
Affiliate Click Tracking with Rack and Redis .
Simple approach to tracking clicks, I probably wouldn't use a list for all clicks, but instead have one for each path, but there's always several ways to get to your goal with Redis. Not exactly the same, but Almaz can track URLs visited …
- GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS: Redis: Data Cheeseburgers
- Ruby Inside: 9 New Ruby Libraries To Check Out
- I can't code! Now what?: Redis is great
- Axon Flux // A Ruby on Rails Blog: How Superfeedr built Analytics using MongoDB
- Running & Coding: LOOP CHAT!
- Engine Yard Ruby on Rails Blog: Custom Chef Recipes with Engine Yard Cloud
The one thing to take from all this? WebSockets are important. You can add them easily to your web applications and build your own, domain-specific protocols on top of them. AND IT'S ALL JAVASCRIPT.
I hope you are excited by now.
NOTE: The server side of WebSockets world is a whole different post. While the protocol itself is ridiculously simple, there are some performance considerations to have in mind. Luckily smarter people than us have already done most of the work. There are …
- Bamboo Blog: The JS model layer
- Bamboo Blog: Custom event emitters in Javascript
- : Sammy.js, CouchDB, and the new web architecture
- Mental Paging Space: ActiveJquery - Status
- AdaRuby: Quest for The Fluid Web Framework
- ronin coder: For all our sakes
If you aren't aware already, HTML5 has Websockets API - enabling bidirectional communication between client and server. You should check Iliya's post Ruby & WebSockets: TCP for the Browser for a better explanation.
Starting with version 0.9, Cramp has in built support for Websockets. Unlike other solutions , Cramp extends the underlying webserver ( thin or Rainbows! ) to add the websockets superpower. …
- Bamboo Blog: A JSON event-based convention for WebSockets
- Bamboo Blog: Living on the edge of the WebSocket protocol
- Ruby Inside: Cramp: Asychronous Event-Driven Ruby Web App Framework
- The messagepub Blog: How-To: Rack Middleware for API Throttling
- igvita.com: Ruby & WebSockets: TCP for the Browser
- Plataforma Tecnologia Blog: Devise: flexible authentication solution for Rails
Support for WebSockets in Chrome and Safari also means that our mobile devices will soon support bi-directional push, which is both easier on the battery, and much more efficient for bandwidth consumption. However, WebSockets can also be utilized outside of the browser (ex: real-time data firehose), which means that a regular Ruby HTTP client should be able to handle WebSockets as well:
require 'eventmachine' EventMachine. run { http …
WebSockets
Yes, I have discussed WebSockets in the previous blog entires and I will discuss more in the following sections.
The many implementations of WebSockets.
I think the node.js evented approach goes very well with WebSockets, but does it mean that we should abandon our favourite server side language/framework? Not quite. Like Jetty and APE already support WebSocket, most concurrency orientated languages, libraries, and frameworks already have WebSocket…
- Bamboo Blog: Living on the edge of the WebSocket protocol
- igvita.com: Ruby & WebSockets: TCP for the Browser
- has_many :bugs, :through => :rails - Home: Websockets made easy with Cramp
I got lots of positive comments/retweets about my last article "Real time online activity monitor example with node.js and WebSocket" .
(if you haven't read the very long article, and not interested into the technical detail, don't worry. I try not to get into technical detail this time )
I am glad that I was able to show how exciting node.js and WebSockets are to make real time web application.
However, I don't think my "activity monitor" example …
- Bamboo Blog: Brain Dump of Real Time Web(RTW) and WebSocket
- MetaSpring Blog: The Double-Edged Sword of Online Transparency
- Pathfinder Development: Pair Programming in the New York Times
- Locomotivation: TweetSaver.com Launched on MongoDB, MongoMapper
- Floehopper: Mocha Test Spies
- Zen and the Art of Programming: Grab DB2 Express-C 9.7.1 now and join the DB2Night Show