Vikrant Gupta

For Fresher level you should follow: 1- prepare C concepts with Let us C and practice with Exploring C by Yashwant Kanitkar. 2- Prepare Quant. with Aptitute by M.Tyra 3- Prepare SQL with SQL/PLSQL by Iwan Beyross. For Experienced follow above steps with following 1. Prepare Java with head first. 2. prepare advance java online by tutorials point.

I am a BCA final year student. Many companies are arriving @ our college for campus. I attended it and...

Framework employs an inverted flow of control between itself and its clients. Frameworks are large bodies (usually many classes) of pre-written code to which you add your own code to solve a problem in a specific domain. Perhaps you could say that the framework uses your code because it is usually the framework that is in control. You make use of a framework by calling its methods, inheritance, and supplying "callbacks", listeners, or other implementations of the Observer pattern. A framework will often dictate the structure of your application. Some frameworks even supply so much code that you have to do very little to write your application. This can be good or bad, depending on how easy it is to use. As Wil Shipley says: Frameworks are the substance of programming. You build on top of a good one, your program is solid and fast and comes together beautifully. You build on top of a bad one, your life is miserable, brutish, and short. A very common example are GUI frameworks, eg Java's Swing and AWT classes. They have a huge amount of code to manage the user interface, and there is inversion of control because you start the GUI framework and then wait for it to call your listeners. The Collections classes are sometimes called a framework, perhaps largely because of the size and complexity. But it is more properly referred to as a library because there is no inversion of control -- your programs simply calls methods in these predefined or extended classes.

Frameworks are large bodies (usually many classes) of pre-written code to which you add your own code to solve a problem in a specific domain. Perhaps you could say that the framework uses your code because it is usually the framework that is in control. You make use of a framework by calling its methods, inheritance, and supplying "callbacks", listeners, or other implementations of the Observer pattern. Framework employs an inverted flow of control between itself and its clients.