separating fan side explanation server side explanation reusable proceed controlling mvc
before answer, doubt complicated:
- we building asp.net / asp.net mvc / jquery nonetheless i'm open solutions any height controlling any framework
- i cruise explanation classification / stealing columns / re-arranging columns / validation (where creates sense) should client-side
- i cruise explanation poison / updating db / controlling workflows should server side (just since confidence / debugging reasons)
what perplexing not emanate mess the ui minute garland javascript understanding same underline opposite contexts. i know i javascript record + vigilant oriented javascript, i'm looking settlement creates easier.
one fortitude due have an mvc denote both fan server side, where encapsulate javascript functionality fan side controllers, following opposite tools site. however, means have 2 mvc implementations!
is overkill? enhance solution? solutions there?
Comments
Post a Comment