Mark Michael's - What Powers Pivotal Tracker: Client side architecture

Mark Michael's - What Powers Pivotal Tracker: Client side architecture

So what makes Tracker work? I will be doing a series of technical blog posts to explain that, starting with a deep dive into the client side architecture. In future blog posts I will highlight Tracker's server side architecture and hosting environment, the external services Tracker uses and what major architecture changes we're considering. Basic principles The client side architecture is the heart and soul of Tracker and is largely based on two user design principles. First, users should not have to "reload" the page or perform any action to see changes made by other users. Second, users should see the affects of their changes immediately without having to wait for the server to respond. Tracker accomplishes these design principles by using a propriety based JavaScript MVC architecture built on top of a command queue. A change made by a user results in a command being enq...

Full article: http://pivotallabs.com/users/mark/blog/articles/1693-what...