Overview

• Home
• Introduction
• Features
• News
• Architecture

Usage

• Downloads
• Tutorials
• License

Community

• SVN
• Issue Tracker
• Mailing lists
• Wiki

Concepts

• AOP
• Syntax-based pointcuts
• Semantics-based pointcuts
• Ontologies
• Our joinpoint model
• Publications

Working on...

• [aPetStore]
• Breakpoint
• Dynamic weaving overhead analysis
• Phoenix
• [SharpDevelop addin]
• Context-Access

Misc

• Existing .NET approaches

Feeds

• Site
• News

Can you summarize AOP in a short sentence?

I can try. AOP proposes a new modularization unit, called aspect, that deals with an application's crosscutting concerns.

What are crosscutting concerns?

I'm not sure there is consensus on this, but AFAIK concerns are basically things you need to worry about when building an application. Crosscutting concerns are issues that need to be dealt with (e.g. users must authenticate) and that are related to many (if not all) of the existing decomposition units (i.e. classes).

What's the basic AOP jargon?

Let's do it the AspectJ way:

• weaver: the guy that's going to get your base code and aspects (rememeber, this new modularization units you have already defined) and weaves them together, so that you get a nice, working system, that deals with all sorts of concerns.
• joinpoint: a given moment during program execution where the weaver is able to do its job.
• pointcut: basically a predicate that defines a set of joinpoints.