<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Websockets on Brave New Geek</title><link>https://bravenewgeek.com/tag/websockets/</link><description>Recent content in Websockets on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 08 Mar 2014 19:18:33 -0600</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/websockets/index.xml" rel="self" type="application/rss+xml"/><item><title>Real-Time Client Notifications Using Redis and Socket.IO</title><link>https://bravenewgeek.com/real-time-client-notifications-using-redis-and-socket-io/</link><pubDate>Sat, 08 Mar 2014 19:18:33 -0600</pubDate><guid>https://bravenewgeek.com/real-time-client-notifications-using-redis-and-socket-io/</guid><description>&lt;p&gt;Backbone.js is great for building structured client-side applications. Its declarative event-handling makes it easy to listen for actions in the UI and keep your data model in sync, but what about changes that occur to your data model on the server? Coordinating user interfaces for data consistency isn’t a trivial problem. Take a simple example: users A and B are viewing the same data at the same time, while user A makes a change to that data. How do we propagate those changes to user B? Now, how do we do it at scale, say, several thousand concurrent users? What about external consumers of that data?&lt;/p&gt;</description></item></channel></rss>