Re^2: Some remarks on the difference between traditional MVC and web-MVC (was: Re^2: Implementing Model-View-Controller)

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

Yup. In fact there is work underway now on complete templating, database persistence and state management using only the browser and Javascript.

Here are some links relating to what ruoso said:

Javascript-only Templating and MVC framework.

Ajax Massive Storage System (supposedly simulate a database without RDBMS or web server).

The point is that "offline AJAX" is a buzzword to be looking out for. Another buzzword "serverless AJAX" might become popular. In fact, with JSON, you can have "offline AJAX without XML" (which is ironic, since XMLHTTP is what started this whole bandwagon in the first place).

=oQDlNWYsBHI5JXZ2VGIulGIlJXYgQkUPxEIlhGdgY2bgMXZ5VGIlhGV

Comment on Re^2: Some remarks on the difference between traditional MVC and web-MVC (was: Re^2: Implementing Model-View-Controller)

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 06, 2006 at 18:16 UTC
Well, but if we go to offline AJAX, then we're getting back to that small system that a simple WebMVC already solves... The question here is having a complex system that you do want to have a server, or yet, multiple servers.. daniel	[reply]

In Section Seekers of Perl Wisdom