From: Steven Ketcham <stedak@...>
Date: 2003-08-26T06:23:12+09:00
Subject: Re: Aspect oriented Everything?

In theory this is true. AOP raises its own tangle of problems (debugging 
when the bug is in the aspect) and I am not sure that AOP at its current 
level of maturity can reduce or simplify a programmer's workload. 
Truthfully I don't know enough about it at this time.

On Tue, 26 Aug 2003 00:02:23 +0900, Volkmann, Mark 
<Mark.Volkmann@AGEDWARDS.com> wrote:

> I think a key point that many people miss about AOP is that it makes 
> classes
> more reusable.
>
> When AOP is not used there are basically two choices for implementing
> functionality like logging, caching, persistence and other so called
> crosscutting concerns.  You can implement them in every class that needs
> them or implement them in a common base class.
>
> Implementing them in every class is bad because if you change your mind
> about how you want to implement them you must change many classes.  Also,

...snip...

>
> AOP avoids these problems.  Since the aspect is separated from the class 
> and
> has nothing to do with the inheritance hierarchy, applications that wish 
> to
> reuse the classes can choose any implementation of the concerns they 
> like,
> including none at all.  This maximizes the reusability of the classes.
>