When working on a web application that involves a lot of JavaScript, one of the first things you learn is to stop tying your data to the DOM. It's all too easy to create JavaScript applications that end up as tangled piles of jQuery selectors and callbacks, all trying frantically to keep data in sync between the HTML UI, your JavaScript logic, and the database on your server. For rich client-side applications, a more structured approach is often helpful. With Backbone, you represent your data as Models, which can be created, validated, destroyed, and saved to the server. Whenever a UI action causes an attribute of a model to change, the model triggers a "change" event; all the Views that display the model's state can be notified of the change, so that they are able to respond accordingly, re-rendering themselves with the new information. In a finished Backbone app, you don't have to write the glue code that looks into the DOM to find an element with a specific id, and update the HTML manually — when the model changes, the views simply update themselves. Philosophically, Backbone is an attempt to discover the minimal set of data-structuring (models and collections) and user interface (views and URLs) primitives that are generally useful when building web applications with JavaScript. In an ecosystem where overarching, decides-everything-for-you frameworks are commonplace, and many libraries require your site to be reorganized to suit their look, feel, and default behavior — Backbone should continue to be a tool that gives you the freedom to design the full experience of your web application.

统一协议，建立连接，开始传输。

Turn your face towards the sun,<br>Let the shadows fall behind you,<br>Don't look back, just carry on,<br>And the shadows will never find you<br>~~

本博客就是我的阅读笔记<br>没有原创全部是从其他地方复制来的<br>介意请不要看，谢谢<br>前期文章有些没有原文地址，深表歉意

请叫我叽歪歪

我私人的java架构交流群：964357187<br>

坚持原创，让心向阳，一路芬芳

左手科技互联网，右手文娱与消费。

获取100本书单，请+：xiaobodushu

TMT名博。人民网、人民邮电报专栏作者。出版有《实战网络营销》《越界：互联网+时代必先搞懂的大败局》等著作。