I was asked to do a short presentation during the PubSubHuddle meetup. The talk was about current development of WebSockets, its issues and building web applications using them.
In the presentation I present the evolution of simple shared-nothing architecture and I try to explain why, in order to use web messaging, the website architecture should be truly asynchronous on every stage. All that is an attempt to express a rationale for the SockJS project. Actually, the full story behind SockJS is much deeper, but probably nobody cares about every detail, I am guessing. The presentation is available here:
The slides are rather terse, in order to understand them you may want to listen to the talk:
For more details about the reasons behind SockJS, read on: