Results 1 -
3 of
3
The Case for Aspect-Oriented Reflective Middleware
- In Proc. of the 6th International Workshop on Adaptive and Reflective Middleware
, 2007
"... The emergence of applications domains such as pervasive and autonomic computing has increased the need for customisation and dynamic adaptation of both distributed systems, and the underlying middleware platforms. Two highly complementary technologies have been advocated to meet these challenges, na ..."
Abstract
-
Cited by 1 (1 self)
- Add to MetaCart
The emergence of applications domains such as pervasive and autonomic computing has increased the need for customisation and dynamic adaptation of both distributed systems, and the underlying middleware platforms. Two highly complementary technologies have been advocated to meet these challenges, namely: aspect oriented programming (AOP) and reflective middleware. However, these have so far been considered in isolation, or typically target a particular middleware challenge e.g. using aspects to customise a middleware implementation; or using reflection (or dynamic AOP) to alter runtime behaviour. We believe that in combination these technologies better support the engineering of dynamic distributed systems. In this paper, we explore how aspects and reflection have been utilised in both the programming language and middleware communities; building upon this work, we identify four core relationships that form the basis of our model for aspect-oriented reflective middleware. We then explore the potential of this model to i) increase support for the engineering of dynamic reconfigurations, and ii) improve the performance of adaptive systems.
Modeling context-dependent aspect interference using default logics
"... Abstract. Explicitly representing aspect interactions is vital so that they can be shared and used in the course of system evolution. As a consequence, guidance can be given to the software developer and automated support for handling interactions becomes possible. In this paper, we propose to use d ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
Abstract. Explicitly representing aspect interactions is vital so that they can be shared and used in the course of system evolution. As a consequence, guidance can be given to the software developer and automated support for handling interactions becomes possible. In this paper, we propose to use default logics for modeling context-dependent aspect interference. We motivate and illustrate our work by an example interference from the domotica world.

