> what is the difference between desgine pattern and a framework? can
> andy body pls give me answer

Framework usually is created to handle some predefined use cases. In order
to be generic enough people define so-called extension points of the use
cases. For example, you have a framework that allows you to create an
e-commerce shop and the extension point would be a possibility to use
different payment methods. Framework defines a standard interface with a
method to do the actual payment. Then you have different plugins, one to
handle payment using credit card, one for bank transfer. You as a developer
can use framework as is, but if you need to accept payments via PayPal, you
just implement that interface and register your class in the framework. Then
the framework will decide when to call your code.

This is so-called "Inversion of Control" design pattern. Design patterns is
more generic concept, the best introduction is "Design Patterns. Elements of
Reusable Object-Oriented Software" by Erich Gamma, Richard Helm, Ralph
Johnson, John Vlissides. It worth reading, but then you can sell the book -
there is enough online resources that contain short versions of all
patterns, it will be enough to refresh all you read. Then you will see
design patterns for object persistence, for developing web applications,
etc. They all show you the best practices to solve some particular issue.

Roman