6 years ago, an article on how to modify VTABLE is made by modifying VTABLE skills, making COM components. That is the concept of my first contact AOP. Through reading that article, just gave me a strong skillful impression. As for the technique of intercepting, this service hierarchy or behavioral expansion, what is the ordinary programmer can bring to us, still moderate. It is only a faint approving, it is very suitable for constructing system-level things, but also a superb technology that may only be used in a particular field. Since I transferred to the Java field two and a half, I have begun to constantly hear fresh AOP, which has become a fashionable programmer. Because JBoss 2003 boldly uses AOP architecture design technology in its 4.0, and the boom of Spring in 2004, I have deeply felt that AOP is already a very important mature technology, it is to master When learning and learning. Through this half-year, it is a common application scenario to AOP, such as Security, Cache, Transaction, and other service cuts, such as Security, Cache, Transaction, etc. But how can AOP use? What should be used? Is it a suitable scene similar to the system service implementation mentioned above? Time to bring such questions, in a Google search, I found a "User" slide of the USE Case and Aspects Working Seamless ToGether "slide. (After a few months I read this slide, the programmer magazine published a Jacobson of the same content). In this slide, Jacobson emphasized his own history of genius and philosophical thinking. In a telecommunications project participated in 20 years ago, I used the idea of today's AOP concept (here. Deeply express their advice to the master). There are several topics in this slide. The component method is not sufficient to solve the software problem When you look at a system with a component method, you see a static structure. We understand the design, implementation, distribution, test, and configuration, etc. of the system. At the same time, components also provide the most important reuse capabilities. But in the components or more underlying objects, there is still a place where it is not so perfect. That is, component / objects and demand are often not the most intuitive and direct mapping, but to be obtained after abstract, analysis, transform, design. The implementation of a requirement often spans multiple components, which is called scattering, and one component itself often contains a number of implementations of multiple requirements, which is called entanglement. Therefore, we need a new way to compensate for / enhance the original object-oriented method. Expansion of the cut surface problem in use
