|
|
Handling Cross-Cutting Conerns - AOP and beyond
With the rise of aspect-oriented programming techniques and tools the issue
of cross-cutting concerns and their efficient handling is becoming more and
more prominent. AspectJ is the most well-known example of aspect-oriented
programming. I have come across many discussions about what constitutes
“real” AOP and what doesn’t. While I certainly don’t have the goal of settling
this discussion once and for all, but I want to widen the scope of the
discussion a little bit: AOP is basically a way to efficiently handle cross-cutting
concerns on language-level. However, there are ways to handle cross-cutting
concerns differently, on other levels, such as design or architecture. While I
don’t want to formally define AO-Design or AO-Architecture, I want to provide
a couple of examples how cross-cutting concerns can be handled without AO
language tools.
|
Publications
