Reply to thread

Message: <blockquote data-quote="AbdulAlhazred" data-source="post: 5485710" data-attributes="member: 82106"><p>Eh, my design philosophy would be to keep the client as dumb as possible. Just send it data to display, lists of choices for the user to select from, and have it send back requests for data and what the user picked. Smart use of training together requests and batching response data should keep the number of round trips fairly low while still allowing the client to be purely View and keeping model and control on the server side. Given that most data is static a decent caching strategy will pay off well too, but noting that how the client does all of that should be relatively transparent to the server side. Once you have a good framework it really isn't that hard. There just have to be a couple of clever people in on the design from day one to architect that.</p></blockquote><p></p>