The case for reflective middleware
Communications of the ACM - Adaptive middleware
Reconfigurable Context-Sensitive Middleware for Pervasive Computing
IEEE Pervasive Computing
Using Architectural Style as a Basis for System Self-repair
WICSA 3 Proceedings of the IFIP 17th World Computer Congress - TC2 Stream / 3rd IEEE/IFIP Conference on Software Architecture: System Design, Development and Maintenance
Reflective Middleware Solutions for Context-Aware Applications
REFLECTION '01 Proceedings of the Third International Conference on Metalevel Architectures and Separation of Crosscutting Concerns
Seamful interweaving: heterogeneity in the theory and design of interactive systems
DIS '04 Proceedings of the 5th conference on Designing interactive systems: processes, practices, methods, and techniques
A Declarative Approach to Architectural Reflection
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
ACM Transactions on Computer-Human Interaction (TOCHI)
Software—Practice & Experience
A component-based architecture for power-efficient media access control in wireless sensor networks
Proceedings of the 5th international conference on Embedded networked sensor systems
Cascadia: A System for Specifying, Detecting, and Managing RFID Events
Proceedings of the 6th international conference on Mobile systems, applications, and services
The Design and Implementation of Open ORB 2
IEEE Distributed Systems Online
PerPos: a translucent positioning middleware supporting adaptation of internal positioning processes
Proceedings of the ACM/IFIP/USENIX 11th International Conference on Middleware
GREEN: a configurable and re-configurable publish-subscribe middleware for pervasive computing
OTM'05 Proceedings of the 2005 Confederated international conference on On the Move to Meaningful Internet Systems - Volume >Part I
| Hi-index | 0.00 |
Traditionally, extensibility and adaptability in middleware is achieved through thorough design of the problem domain. The key variability points are modeled at design time to allow plugin of new functionality at different points in the system. Unfortunately, it is historically shown that the actual adaptability needs at some point differs from the ones predicted. We argue that the seams, which are hidden in middleware with seamless design, should be accessible for pervasive computing application developers. It cannot be foreseen which aspects of a seam the domain or application need. We suggest that in addition to modeling the domain variability points the middleware should expose a model of the internal processing mechanisms of the middleware itself. The middleware should support modification of this model. Furthermore, at all places where the middleware achieves the normal seamless use of the domain, the model should be adaptable and adaptations should be absorbed into the middleware. We present model-based translucency as a middleware construction goal. The supporting arguments are given and examples of use of models in middleware are compared to the requirements for which we argue.