My view is that unless you need to change the basic structure of the user interface, you should not have to reload the page at all for any user interactions.
I’d like to approach my next ASP.NET MVC project with this in mind. Can anyone suggest any principles, patterns or practices* I should consider?
- Excellent book, btw. Still trying to wrap my head around some of the concepts though. I thought a question like this would help link the theory to a practical design.
edit I should also mention that I intend to use jQuery to handle the asynchronous client/server interactions. Specifically, I’d like suggestions on archetectural considerations to keep in mind
Thanks
Indeed, AJAX, you can do everything on 1 page, it’s not really difficult at all once you get the basics.
There are some challenges/downsides though:
Search engine optimisation is a non-starter, if you want to rank on google with a single ajax page, you’ve got a lot of hard work agead.
Browser history, broweser history is important to the user experience, so you will need to tackle it, it’s not that hard to implement with ajax content though.