angularjs and ASP.NET MVC : best strategy for clientside models -


i'm looking client side model binding html templates angularjs. wondering best strategy retrieving clientside viewmodels server, e.g. viewmodel containing not data editing data select lists or drop down lists etc..

as see , 1 has several options

  1. retrieve 1 viewmodel server using e.g. web api, containing data needed view model
  2. render client side viewmodel javascript inside server side html
  3. retrieve data viewmodel using multiple web api calls, e.g 1 main data edited, , 1 each additional data (select lists)

i didn't encounter many examples option 1 seems web api used crud operations returning specific data 1 type of object e.g. person or order

option 2 conforms practice of server side view models asp.net mvc have not seen many examples using technique in combination angularjs

option 3 looks clean if 1 considers seperation of concerns, has disadvantage of multiple smaller ajax requests.

could share thoughts , experiences ?

i agree st. never , have used option #3 , think combining $resource , web api perfect rad combination. however, i've worked on complex screens i've wanted sub-second response times i've resorted optimise entire development 'column' - develop using sql server backend database i've used it's native support xml return structured xml stored procedure serialise .net model (poco) pass json serialiser transfer browser. might have business processing perform against poco still leads simple code structure transfer complex structure of data. typically it's fast because i've made 1 call database , monitoring , optimising 1 stored procedure simple.


Comments

Popular posts from this blog

c# - Send Image in Json : 400 Bad request -

jquery - Fancybox - apply a function to several elements -

An easy way to program an Android keyboard layout app -