Comments on: The next big thing, part 1: Resolving the conflict between Model-View-Controller and AJAX design patterns

By: Another browser-side Model-View-Controller analogy

Another browser-side Model-View-Controller analogy — Wed, 07 May 2008 21:53:22 +0000

Coding Horror presents another way to think about the browser side of web apps as underlyingly MVC in Understanding Model-View-Controller. It's interesting, but I still prefer my analogy for primarily AJAX web apps; when the data comes in primarily through XMLHTTPRequest, it doesn't make much sense to think of anything but the JavaScript that handles XMLHTTPRequest responses as the model.

By: The two ugly faces of HTML generation

The two ugly faces of HTML generation — Tue, 18 Mar 2008 07:36:55 +0000

If you are building an AJAX app, you’ll quickly find that it’s easiest to query for all of your algorithmically generated or database data and convert it to HTML with JavaScript….

By: Internet, meet Spydentify

Internet, meet Spydentify — Wed, 20 Feb 2008 01:24:06 +0000

The interface also follows the MVC pattern I laid out in this article. It uses one static HTML file, all dynamic data is loaded through XMLHTTPRequest, and all HTML generation is done via JavaScript manipulation of the DOM…