Several months ago I was in sort of a chaotic mood:
I knew MVC (model-view-controller) paradigm conceptually but simply could not "get it". The strict nature of MVC and transiency and statelessness of the web was not quite fitting together in my mind.

I am from a OO/Java background and I believe I'm good add playing with objects, polymorhpism, encapsulation and all the stuff like that. However MVC is something deeper than OO. And there is only one way to understanding it:

Getting Your Hands Dirty

Anyways, in those days I've scribbled my thoughts about what MVC should be like in web applications where AJAX acts as a stub between the view and the controller. It's not much like an article. More of me talking to myself in MVC.

I used and evolved the paradigm in for several months (may be I will write an article on that when I find time).

And recently I've read a codeproject article explaining the issue in a more -how to say- comprehensive manner.

But the core idea was the same. The article demonstrated me once again that my argument, on how I considered MVC should be implemented in contemporary web applications, was stable and logical.

I picked two more codeproject articles for the interested (links 3 and 4)

Links:

[1] "A Paradigm shift in MVC"

[2] "Improving the design pattern of web applications with AJAX"

[3] "Applying Robustness Analysis on the Model–View–Controller (MVC) Architecture in ASP.NET Framework, using UML"

[4] "Development of web application using MVC II design pattern or why following MVC II will help me"

HTH.

 bu yaziyi sevdin mi?  hemen una ekle!