Buy Onkyo Reciever In Us And Use It In India

AOP (Aspect Oriented Programming)

The Aspect Oriented Programming (AOP) is a programming paradigm relatively recent whose intention is to allow adequate modularization of applications and enable a better separation of concepts. Thanks to the POA can encapsulate different concepts that make up an application in well-defined entities, eliminating the dependencies between each of the modules. This will get better reasoning about concepts eliminates the dispersion of the code and the implementations are more understandable, adaptable and reusable. Several technologies with different names are aimed at achieving the same goals and so the term POA is used to refer to various technologies such as adaptive methods , the filters composition, the subject-oriented programming or multidimensional separation of powers.

Basics

• Aspect (Aspect ) is the function that crosses over the application (cross-cutting) that will be implemented in a modular and separate from the rest of the system . The most common and simple example of an aspect is logging (Event Log) into the system, since it necessarily affects all parts of the system to generate an event.
• Jointpoint ( Crossing Point) is a point of execution within the system where a point may be connected, as a call to a method, throwing an exception or modification of a field. The aspect code is inserted into the flow of execution of the application to add functionality. Advice
• ( Council) is the implementation of the aspect, ie, it contains the code that implements new functionality. Are inserted into the apliacción in Crosspoints. Pointcut
• ( Cutting Points) defines Tips that apply to each crossing point. Specified using regular expressions or by patterns of names (of classes, methods or fields), and even dynamically at run time based on the value of certain parameters. Introduction
• ( Introduction ) lets you add methods or attributes to existing classes. An example that would be useful is the creation of a Board of Audit to keep the date of last modification of an object through a variable and a method setUltimaModificacion (date), which could be introduced in all classes (or just some) to provide this new functionality. Target
• ( Recipient ) is the recommended class, the class that is the subject of a council. Without AOP, this class should contain the logic as well as the logic of appearance. Proxy
• ( Resulting ) is the object created after applying the Council to the recipient object. The rest of the application only need to support the Object Receiver (pre-AOP) and not the resulting object (post-AOP).
• Weaving is the process of applying aspects to recipient objects to create new objects resulting in Crosspoints specified. This process can occur throughout the cycle Recipient Object Life: Aspects
  • Compile Time, you need a special compiler.
  • aspects at load time, the aspects are implemented when the recipient object is loaded. Requires a special ClassLoader.
  • aspects at runtime.