What is best structure for a big application?

[eluser]Edemilson Lima[/eluser]
The MVC way of coding forces us to build every module of our application in strings first, and in the end it put everything together to send to the client. I am wondering if this is not a waste of web server's memory. The old way of building PHP web sites using include() and require() makes PHP to flow a logic order and it just build the whole page in a buffer to output after, if the output buffering is on. With a MVC, don't we need to take more care about the strings and arrays we use to don't spend more memory than necessary? Could a Nested MVC help us on this, by automating the process of collecting the return of each module?


Please continue reading about this subject in the following post:

http://ellislab.com/forums/viewthread/70425/P0/