Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Preparing data in json format on backend and populating data to templates via ajax on frontend, what’re the problems with this architect design? Assume all visitors use javascript-capable browsers, and we don’t care about the number of HTTP connections that a webpage has to make.
That architecture is fine, in fact it is the architecture enforced by some frameworks like javascriptmvc.
Just some comments:
Depending on the complexity of the templates the rendering can be slow in the client side.
If you have a lot of simultaneous requests from the same client to get data, they will be queued to keep a maximum of two simultaneous requests delaying the page load.