- Keeps things separately : database in controllers, code separately, etc. - Easy to maintain edit - Faster - Some kind of templating - Caching - Code re-using
what are you fishing for? If you can't extrapolate what functionality would be NEEDED from crivion's post, you are wasting his time and everybody else's as well. http://en.wikipedia.org/wiki/Software_framework http://en.wikipedia.org/wiki/Web_application_framework
I'd look to organise, improve and extend the core functionality of the language I am trying to write a framework for - there is no sense in providing things that are already implemented to a satisfactory level out of the box, other than to satisfy the need to produce code that is structured similarly throughout. Basically, look to export all tasks you are likely to reuse over and over again into the library - program to patterns.
Suppose I developed an application in any of MVC framework of PHP. Now I have to distribute that application, do the client need to have the framework too ?
ya. kinda like here's your new car. Where's the engine? could look at Joomla as an example, if you build a component for it: gotta have joomla to use it.
the client - if defined as "the browser" - no. the client as the recipient of your work and owners/admins of the site/domain - yes, the framework will have to be installed. with JS frameworks, for example, the clientside browser needs to download a copy of the framework also.