Discussion on:

MVC design pattern brings about better organization and code reuse

Interesting article - reminded me of how I used to get people to structure thier code in good-old non-web applications. Still highly relevant for server-side applications, but I do prefer multi-tier applications nowadays, they allow you to isolate the database from the business rules (if required) allowing porting to a different back-end by just changing the data interface layer

This article doesn't tell me anything about MVC that I didn't know before and is extremely lacking in detail, not even a link to a good technical desription, anyway what ever happened to n-tier development, IMHO MVC should be left to the user interface only.

hmmm...well cs1mis, I'd be happy to read YOUR next article or book. In case you didn't notice, builder prints 1 or 2 page articles...if you want more details, buy a book. Oh and I guess you failed to notice the link to Sun's J2EE MVC pages at the bottom of the article. I won't bother pointing out the error in your assessment that MVC should be for interface only (that's the V part, but you claim you already knew that?)

Regards,

Brian

I'm going to have to go with Brian428 on this. You obviously like to type before you read. Also, your humble opinion, interestingly enough, is what we call a big "no kidding!" but thanks anyway.

MVC can be extremely complicated and I think the intention here it to intice you to research on your own. Additionally, MVC can be a part of n-tier development.

Upon re-reading your post I am wondering if you posted to the correct article. It's almost like you didn't even read this one. Certainly, your knowledge of MVC with respect to n-tier development is lacking. I suggest the following link to learn more about MVC (in addition to Java's page): http://ootips.org/mvc-pattern.html.

MVC sounds to me like a multi-tiered design. I agree with the author in everything but one point. I use this design pattern for all projects, not just large ones. Even in the smallest of applications, requirements change without too much notice.I've proven to myself over and over again that using multiple tiers saves me work in the long run.

The author is correct when mentioning complexity while using ASP, VBScript, etc. that has no open source community backing to create a forum for reusable frameworks, so implementing things yourself is just about the only option. Even so, implementing Model 1 MVC is fairly trivial even if it is not as elegant. It is just you and M$. Of course there are as many as a dozen MVC frameworks available for the Java platform, so once again I question where the huge amount of complexity comes in. I wouldcertainly question one's prowess in development if Jakarta Struts had an even remote 'learning curve'. It should appear instantly obvious.

Complexity isn't driven, for the most part, by the language you choose to implement your solution. Rather, the author was trying to convey the fact that the you may find the implementation of this methodology too time consuming to be justified for asmall project, especially when you have deadlines and limited time/resources and when unmet deadlines will cost your company money.

Great article!

MVC as it was originally planed, straight to the point,

I liked it a lot!

You can read about using MVC in modern IDE?s in
http://aviadezra.blogspot.com/2007/07/twisting-mvp-triad-say-hello-to-mvpc.html

A very useful introduction to the pros and cons of the MVC design pattern (mostly pro's of course 'cause the MVC is great).

Nicely done Brian Kotek!

Thanks Kotek for all ur explanation.Even if it doesnt cover all cons of MVC it surely gives us direction as to what kinda applications we should develop using MVC.

The MVC pattern is a useful addition to a toolkit, no matter what language you choose. But among its many benefits, it does have some drawbacks. paycheck loan

plz,
if anyone knows about how to implement faceook or twiitter or blog using mvc then tell me.
i dont want all exact implementation but just overall idea about what model,view & controller will contain generally

I'd like to thank you for this well written article. Everyone implements MVC in a slightly different way, but this article makes the separation between the Model, the View, and the Controller very clear.

A must read i would suggest