Posted on 2013-12-25
I'm rewriting a 2005-era ASP.NET app that currently does most of the display formatting on the server by building HTML strings which are then sent via xmlhttprequest to the client.
I can see how I might use MVC/Razor/JQuery/JSON/AJAX to just send the data content to the client, and let the client do the DOM display object construction, even if it requires a good bit of business logic.
> For this application a "large" completely formatted div in the app might run 500K of HTML of which no more than 50K of data would be data (average would probably be more like 250K and 25K). There could be three such divs being displayed (overlapping) at any one time (along with a few much smaller ones, essentially popups).
> I'm hoping to run the app on PCs, tablet and phones.
What I'm hoping to find from EExperts is:
==> input/ideas/views on how to decide whether to put the display logic in the client, or keep it back in the server.
Any help with this would be appreciated.