This is the last question from Quiz on Design Pattern on website by Marcus Green.
Your junior designer has bought you a design that embeds html in print statements and you are concerned that the business and presentation logic are tightly combined. You are concerned that this will make it difficult to modify the display without touching the business logic. Which design pattern could you recommend to help separate presentation design from business logic?
I was able to figure that the design pattern has to be either MVC or front controller. Could someone help me understand why the design pattern here is Front Controller and not MVC ?
Doesn't this line from the question "Which design pattern could you recommend to help separate presentation design from business logic?" a good reason to say that MVC suits the given criteria?
Ezhil S Alagesan
Joined: Aug 31, 2007
The below stuff is taken from peabodyonscwcdpatterns doc on Front Controller A centralized access point for presentation-tier request handling. Forces * You want to avoid duplicate control logic. * You want to apply common logic to multiple requests. (IF) * You want to separate system processing logic from the view. (MVC) * You want to centralize controlled access points into your system. (IF)
Could anybody infer something with this piece of information.