-----Mensagem original----- De: Stephen McConnell [mailto:[EMAIL PROTECTED]
1. interdependencies between aspects - My feeling is that as aspect is independent, and if a dependency is identified, then in fact your not looking at an aspect - instead its a system of some kind. I also think you cannot deal with aspects in a completely generic way - because I think aspects start to make sense with a specific and concrete context (for example - the "management aspects" of a component model). Establishing a common context also means that you can eliminate things that may initially be considered a dependency.
Ok, a SystemContext is your suggestion. I agree.
That's an example a particular context. Just at the moment I'm thinking more generally, but yes - something like SystemContext or others such as ContainmentContext establish a frame of reference within which a aspect starts to take on relevance. My hunch is that aspects will start to make sense when we look at "orthogonal" concerns relative to the object model. For example, I think we can consider change notification as orthogonal to the subject a particular instance of a configuration.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
