Hi Tom,

Security is one of the most commonly used examples for AOP as it is a cross
cutting concern that most developers are familiar with. I would definitely
look at using AOP for security.

Best Wishes,
Peter 


On 6/25/07 5:51 AM, "Tom Chiverton" <[EMAIL PROTECTED]> wrote:

> On Saturday 23 Jun 2007, Sean Corfield wrote:
>> There's nothing wrong with circular dependencies in OO systems.
> 
> With that in mind, I've just used an injected fooManager in a securityManger
> to get a foo record and check access permissions. The fooManager calls the
> securityManager to check permissions :-)
> 
> It's just occurred that an Advisor could check the incoming operation (edit)
> and object id and throw an exception itself... is that a good idea,
> generally, or over doing things ?




Reply via email to