A message-oriented middleware for sensor networks
MPAC '04 Proceedings of the 2nd workshop on Middleware for pervasive and ad-hoc computing
A Style-Aware Architectural Middleware for Resource-Constrained, Distributed Systems
IEEE Transactions on Software Engineering
A Perspective on the Future of Middleware-based Software Engineering
FOSE '07 2007 Future of Software Engineering
Programming wireless sensor networks with the TeenyLime middleware
Proceedings of the ACM/IFIP/USENIX 2007 International Conference on Middleware
AME: an abstract middleware environment for validating networked embedded systems applications
HLDVT '07 Proceedings of the 2007 IEEE International High Level Design Validation and Test Workshop
Scalable Message Translation Mechanism for the Environment of Heterogeneous Middleware
IEEE Transactions on Consumer Electronics
Hi-index | 0.00 |
The extreme heterogeneity of networked embedded platforms makes both design and reuse of applications really hard. These facts decrease portability. A middleware is the software layer that allows to abstract the actual characteristics of each embedded platform. Using a middleware decreases the difficulty in designing applications, but programming for different middlewares is still a barrier to portability. This paper presents a design methodology based on an abstract middleware environment that allows to abstract even the services provided. This is gained by allowing the designer to smoothly move across different design paradigms. As a proof, the paper shows how to mix and exchange applications between tuple-space and message-oriented based middleware environments.