resource dependency splitting

tighter encapsulation of dependencies via an inner/outer model
thoughts about the web socket connection host

not sure how i want to do this anymore... kinda want to make a mixin
interface here?  not sure, not sure
prettying it up
silly little change

this whole API needs a wash.  badly
Merge branch 'feature/general-cleanup' into develop