In many ways that's the case. Presentation components reside entirely on the client. They can be delivered to the client via a server as a deployment mechanism, but at runtime, and interacting with services, the View components are entirely on the client. They're not bound to data on the server, and delivered in that sort of composite, html format that most server page models, and template models make use of. And it's not a knock against those models: that's the html model, that's what http requires, and there're some advantages to that. And the browser by-and-large doesn't let you do much more than that. So Rich Internet Applications eliminate that collection of View and Model on the server altogether and enforce a fairly clean separation so that on the client, you're directly interacting with your remote services.