under an mvc framework, office structure approaching developers?


generally, mvc frameeworks have structure looks something like:



/models
/views
/controllers
/utils


however, web concentration suite, i've solid clumping models, views, controllers together substantially wouldn't best clarity, unless i treated component concentration instead an concentration suite. however, things tie each "application" together, thought users user roles.



so i have 3 illusory solutions:



(1) i don't unequivocally wish do, keep each model, view, controller together, regardless app belongs to. treating unit unparalleled application, given tied together several common threads, including users.



(2) organisation formula application.



/app1
/models
/views
/controllers
/utils
/app2
/models
/views
/controllers
/utils


(3) organisation formula type, permitting concentration formula common among applications.



/models
/app1
/app2
/views
/app1
/app2
/controllers
/app1
/app2
/utils


is there an choice i missed? many judicious amour destiny developers? i personally move 2 3, nonetheless maybe many design 1.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members