By Adam Wulf on September 21, 2008
Also posted on the Listotron Blog
Imagine for a moment that you’re building a web application based nearly 100% percent on AJAX. And imagine that you’ll likely need to send bursts of multiple AJAX requests to your server, and you also need all of these requests to be processed in order when they hit your server. You want a near continuous AJAX connection – every action, every edit, every keystroke the user makes – all of these need to be sent to your server for processing. You are building Listotron.
By Adam Wulf on August 18, 2008
I just finished the next phase of my jQuery MVC Tutorial series. This time, I walk through how to save, edit, and delete data via AJAX with an MVC pattern. One of the major take aways from this one is showing how easy it is to roll-back the View in the unfortunate event of an AJAX request failing.
By Adam Wulf on August 5, 2008
Search Google for “web application MVC patterns” or any variant thereof, and the vast majority of results will talk about the server side MVC. This traditional answer will tell you the browser sits outside the MVC altogether, and sends in HTTP requests that are handled by the Controller, then all the MVC garble happens, and finally the View spits out a brand new HTML page (or XML/JSON for AJAX) for the browser to consume. All this ends up looking something like: