title: EmberJS multiple statemanagers/routers
body: <p>Is it good practice to have multiple statemanagers for the purpose of splitting up multiple outlets that need to maintain separate functionality?</p>
  
  <p>Examples: </p>
  
  <ul>
  <li>iPad style popover windows (http://metalabdesign.com/images/screenshots/flow-inside.png) - this is a separate controller and view then the current state. It makes sense to me to have a "popover statemanager" - that way the router still stays in its current state when the popover is opened - all the other buttons and actions on the page still work...</li>
  <li>Modal windows, dynamic sidebars, etc...</li>
  </ul>
  
  <p>My thinking is to have a router the controls the main interaction and it simply fires off commands to statemanagers that break up certain "sections" of the current "screen" to isolated parts.</p>