So this is an idea I hadn't considered - having one model per each settings tab.  I was imaging having one `SettingsModel` for all settings, instead of broken up by tab.  

Having separate models for each tab is nice in that it breaks up functionality for each tab.

However that also doesn't seem like the way a model should be used.  There should be one model for one resource type, and all relevant data attached there.

What are your thoughts re: having `/models/settings/<tab>.js` vs `/models/settings.js`?