Thanks for your explanation, I am trying to show someone how much easier life is with the separation of logic, views and database. This is one of the best ways to explain it that i've seen that didn't make it confusing.
I am not totally agreed with your explanation. This is good to understand the layered programming not the MVC. I would say, this is more relevant to N-tier architecture. Here it is not clear about either Model, View or Controller. Can you please explain what is the role of Model, View or Controller and how it is different from N-Tier architecture.
Thanks for sharing - much appreciated! Could you please refer me to your earlier post where you explained whatt MVC is - I can't seem to find it? Thanks again :-)
Thanks for such a nice explanation... really enjoyed it.
ReplyDelete[...] http://www.anil2u.info/2011/11/understanding-the-basic-need-of-mvc-architecture/ [...]
ReplyDeleteThanks for your explanation, I am trying to show someone how much easier life is with the separation of logic, views and database. This is one of the best ways to explain it that i've seen that didn't make it confusing.
ReplyDeleteThanks
Shawn
http://blog.s-vizion.com
wow..such a great explanation about MVC..really i njoyed with this..thanx for sharing
ReplyDeleteThanks
Gopi
Excellent Explanation Anil
ReplyDeleteExcellent explanation sir with neat diagrams
ReplyDeleteI am not totally agreed with your explanation. This is good to understand the layered programming not the MVC. I would say, this is more relevant to N-tier architecture. Here it is not clear about either Model, View or Controller. Can you please explain what is the role of Model, View or Controller and how it is different from N-Tier architecture.
ReplyDeleteExcellent Article!!
ReplyDeleteThanks for sharing - much appreciated! Could you please refer me to your earlier post where you explained whatt MVC is - I can't seem to find it? Thanks again :-)
ReplyDelete