ember.js - Best practice for application-wide states in ember? -


  1. should use separate controller sessioncontroller, , pass around desired variables other controllers using needs: hook?

this seems un-dry quickly.

a simple internal variable #1 won't reflected in url. can save database seems costly , silly gets changed part of app experience, opposed infrequently changed user setting.

it seems best way reflect state in url 1 way or another.

  1. or should have dynamic segment parent url segment routes?

if go option 2, how obtain , remember subroute url segments when using transitionto or link-to?

  1. or should change query parameters in such way sets regardless of route may in?

would cause conflicts or management hassles if you're using other query parameters, or can cleanly append , remove individual query parameters?

or there better way handle such things?


Comments

Popular posts from this blog

Payment information shows nothing in one page checkout page magento -

tcpdump - How to check if server received packet (acknowledged) -