title: Understanding the relationship between controllers and routes in Ember
body: <p>I'm having a bit of trouble understanding the conceptual relationship between controllers and routes in an Ember application.</p>
  
  <p>I've started down the path of a pretty simple spike test to evaluate Ember, and the deeper I get into it, the more I'm seeing my routes fill up with what I'd have through should be the controller's responsibility, such as actions, wiring up models, and ultimately dispatching to a view to render a template.</p>
  
  <p>The controllers are all empty, and seem to be just a placeholder for some auto-mapping requirement.</p>
  
  <p>Am I missing a fundamental thing here - coming from a Rails perspective, and applying (perhaps erroneously) the "rails way" to Ember I expected my routes to define states that are represented by URLs, which would map to a controller "action".</p>
  
  <p>Any pointers would be much appreciated.</p>