Our Architect wants our MVC2 application to use a frame-set with header, navigation and content frames.
His reasoning is that the content of the header and navigation frames need only be loaded once whereas with master
pages, ignoring caching, the whole master is loaded each time you visit.
Having looked around, it seems to me that few (if any) MVC users resort to frames and can't help but feel that frames
isn't the way to go. What are your general views on this?
If we were to accept the Architect's reasoning, I'm unclear as to whether we dispense with the master page or whether
there's a way to make a master page work with a frame-set. Does anyone know of any resources that show best practice
when using frames with MVC applications?
View Complete Post