[aosd-discuss] getting a more complex aspect from simpler ones....

[Jörg Kienzle]

Hi,

in our paper "AO Challenge - Implementing the ACID Properties for  
Transactional Objects" in the last AOSD conference we define a set of  
ten base aspects, each one providing a well-defined reusable  
functionality needed for implementing the ACID properties of  
transactional objects. The base aspects are simple, yet have complex  
dependencies among each other. We then show how these base aspects  
can be configured and composed in different ways to implement  
different concurrency control and recovery strategies -- lockbased,  
lcokbased-multiversion and optimistic. Of course such a composition  
is delicate, since some aspects conflict with each other.

- Jörg

J. Kienzle and S. Gélineau, “ AO Challenge: Implementing the ACID  
Properties for Transactional Objects,” in Proceedings of the 5th  
International Conference on Aspect-Oriented Software Development -  
AOSD 2006, March 20 - 24, 2006, pp. 202 – 213, ACM Press, March 2006.

On 23-Oct-06, at 1:10 PM, ffs at ita.br wrote:

> Hello,
>
>    Some time ago, I have exchanged some emails with Dr. Pawlak and  
> other
> researchers about some aspect composition issues.
>
>    The main idea is get two or more aspects composed in order to form
> another one more complex (i.e. a+b=c).
>
>    Let me try to be a little bit more clear: the idea is to get an
> example of two aspects that are composed in order to form/build  
> another
> one more complex. One example would be:
>
>    Persistence (a) + Distribution (b) = Replication (c)
>
>    So, what do you think about that? Where can I find out more  
> examples
> where this approach has been somehow applied?
>
>
> Regards,
> Fabio
>
>
> _______________________________________________
> discuss mailing list    -    discuss at aosd.net
>
> To unsubscribe and change options, go to:
> http://aosd.net/mailman/listinfo/discuss_aosd.net
>
> Check out the AOSD.net Wiki: http://aosd.net/wiki