Aspect-Oriented Programming (AOP) presents the principle of the separation of concerns, allowing less interdependence, and more transparency. Thereby, an aspect is a module that encapsulates a crosscutting concern, and it is composed of pointcuts and advice bodies. The interception of an aspect is performed in a join point (a point in the execution flow), and defined inside a pointcut (a set of join points). Whenever the application execution reaches one pointcut, an advice (namely a callback) associated with it is executed. However, this implementation does not take into account separation of concerns in distributed settings.
In contrast, distributed AOP is a promising paradigm that allows distributed interception. It defines many new concepts like remote pointcuts, which are similar to traditional remote method calls, since execution is performed on a remote host. Thus, distributed AOP establishes a context where aspects can be deployed in a set of hosts. In this sense, the remote pointcut abstraction is considered the starting point for distributed AOP. After that, some works have extended this idea in some way, but all of them share the concept of remote pointcut.
A distributed aspect is defined as a crosscutting software module that may operate in multiple remote hosts to intercept and alter the whole behaviour of a distributed application. This distributed entity is able to modify or adapt the distributed system by applying additional functionalities (remote advices) at various hooks located in different hosts (join points) and triggered via distributed connections (remote pointcuts).