anchor.diff:  }</code></pre>
   </div>
   </div>
  +
  +<p>Each <b>server controller</b> has a <b>routes</b> and <b>post_routes</b>
  +method that tell the app where to find the handler for that given sub-route.
  +</p>
   
   <h3>MVC</h3>
   
  
positive.code: 
    <p>
    In superfluous, the server is composed of
    <a href="http://www.senchalabs.org/connect/">connect middleware</a> running on
    <a href="http://nodejs.org">node.js</a>. The server is responsible for
    sending <b>apps</b> (a <b>page</b> can be considered a type of app) to the
    client.  Each server can host one or more web apps, each living at its own
    top level URL.  </p>
  
    <p>
    In addition to delivering the app to the client, the server is generally
  
negative.code:   </p>
  
    <p>
    <b>Re-usability</b> - Components are <b>Backbone.Views</b> that encapsulate
    re-usable portions of rendering, event handling and data synchronization
    code. Using components on a site adds structure, well defined behaviors and
    division of responsibilities. Every component is responsible for managing its
    sub DOM, so the responsibilities are clear cut.
    <br />
  
    <div class="alert">Many large web codebases today are using Component based
  