[aosd-discuss] Are frameworks crosscutting?

[Sean Gilbertson]

     I've been pondering (and testing) whether I can put all the  
interaction with core logic ("model" logic) into an aspect, and have  
the aspect notice changes in the UI and the model, and act  
appropriately.  So for example, if you had a client to a server, the  
aspect would notice when someone clicks "connect" via a pointcut on a  
method in the controller which responds to the button-click (and  
proceeds to set labels to "connecting..," etc.), and then call a  
method on a (singleton!) instance of the client, to connect.  Then,  
when something happens to the model, like an unexpected disconnect,  
the aspect monitors a method in the client class (e.g.  
"disconnected"), and tells the UI(s) about it (i.e. by calling a  
"gotDisconnected" method or something).  This may be inelegant for  
whatever reasons, but it's intriguing to me.  You could perhaps even  
separate elements of a package, or intersecting packages, this way.   
In this manner, you could "plug in" functionality whenever and  
wherever you want.

On Apr 26, 2005, at 1:55 AM, Paul Soule wrote:

> Hi,
>
> If we have an OO framework, that framework's code is contained in  
> all classes that inherit from, or contain, that framework. When  
> used, the framework's code will crosscut a system's functionality  
> because it will be contained in any class that uses the framework.
>
> Is it therefore true to say that all concerns contained in a  
> framework are inherently crosscutting in nature because the  
> concerns will, via inheritance or containment, be scattered through  
> an application that uses the framework?
>
> Thanks,
> Paul
>
>
> __________________________________________________
> AOSD Discuss mailing list    -    discuss at aosd.net
> To unsubscribe go to http://aosd.net
>
>