[eluser]Michael Ekoka[/eluser]
Quote:I really dont think it would be as hard as you guys are making it sound. You have normal pages like every application, then you have some ajax methods in your controllers.
The technique to create an ajax request is easy. Now, having a methodology to integrate and manage Ajax requests over an entire web site in a safe and standardized way, is what may represent a challenge. Which is the reason why it is better to adopt a sound approach to ajax development from the beginning. If you only want to add a few little functionalities here and there, you don't need much protocol, true. But, what about replicating in ajax 80% of already functional processes throughout your app. You can't possibly do this without a plan. Proceed carelessly and a few dozen actions later you end up with an application that breaks in the most unusual ways as soon as the user "tests" it with javascript off.
JosGo came up with a flowchart illustrating his (her?) approach to ajax in the MVC context. I simply shared 3 general methodologies that attempt to minimize the consequences of running a javascript based application on a non-javascript environment. Most people nowadays don't have a real reason to disable js in their browser, but we all know that we should never trust the user.
