Best paractices or guidelines for MVC Framework

[Pratibha Malhotra]

Can any body please let me know about best practices or guidelines to design a MVC Frame work..
What all points should one take care off

[Lasse Koskela]

Here are some properties to think about:

Extensible -- the framework should allow for a wide variety of customization

Non-disruptive -- the framework shouldn't prevent using another framework within the same application

Helpful -- the framework should incorporate common functionality for improving overall productivity

Simple -- the framework should be relatively easy to learn and use

Clean -- the framework should separate concerns (e.g. deployment-specific configuration should be separate from code)

There must be more, but I hope this is an ok start...

[Ilja Preuss]

The best way to make sure that your framework actually is usefull and usable is to concurrently write at least two or three different applications that make use of it.

[Kishore Dandu]

Struts is almost proven in that sense with respect to MVC framework.
In the near future, a combination of JSF and Struts can be very productive to develop cool web applications.
Kishore.

[Michal Harezlak]

MVC is a pattern (best practice) so I would get you familiar with it to get best possible understanding of it. Then you go and choose a framework or write your own. Then you write guidelines what to be aware of when using your framework and make it known (difficult part). In case [e.g.] you choose Struts, it could look like this:
Things to remember when with Struts:
�Only one instance of Action class is created
�Watch for thread safety
�Use local variables
�Do not synchronize your method if you do not have to it can be major performance bottleneck.
Hope that helps.

[Ilja Preuss]

Gunjan, why do you ask?