in reply to Re: Some remarks on the difference between traditional MVC and web-MVC (was: Re^2: Implementing Model-View-Controller)
in thread Implementing Model-View-Controller
Unless you get serious about AJAX (many people bet on this).While you can certainly craft stuff on top of AJAX that behaves like a callback system, it's still running on top of HTTP, i.e. request/response pairs originating from the browser.
That means you're still just polling for data from the client as soon as you need any information from the server side. You're not pushing data to the display as you do in traditional GUI applications, where the view also knows a lot about the state of the display. Actually, my guess is that the more AJAX technology you're using, the more you'd have to focus on plain output & http caching if you want to get any kind of performance (instead of generating one HTML page, you're generating lots of XML fragments).
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Some remarks on the difference between traditional MVC and web-MVC (was: Re^2: Implementing Model-View-Controller)
by ruoso (Curate) on Jan 05, 2006 at 17:22 UTC |
In Section
Seekers of Perl Wisdom