Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Monitoring, security, and dynamic configuration with the dynamicTAO reflective ORB
IFIP/ACM International Conference on Distributed systems platforms
The case for reflective middleware
Communications of the ACM - Adaptive middleware
Proceedings of the IFIP TC6/WG6.1 International Conference on Open Distributed Processing II
Adaptive Resource Management in Middleware: A Survey
IEEE Distributed Systems Online
The design of a configurable and reconfigurable middleware platform
Distributed Computing
Develop once deploy anywhere achieving adaptivity with a runtime linker/loader framework
ARM '05 Proceedings of the 4th workshop on Reflective and adaptive middleware systems
| Hi-index | 0.00 |
Distributed systems that dynamically adapt to changing environments should be developed based on incrementally defined, loosely coupled services. But current middleware platforms tend to encourage monolithic services that are tightly coupled with their environments. We suggest that the non-incremental nature of middleware services is due in part to the lack of support for implementation inheritance, and that tight coupling is due to insufficient support for interface abstraction. Interface-oriented programming (IOP) is an extension of object-oriented programming in which all program inter-dependencies, including inheritance dependencies, are expressed using interface abstractions. This encourages development of partial classes, and requires a new program linking mechanism called representation inference to integrate them. We propose that a distributed implementation of IOP including partial services and distributed service inference could address some of the limitations of middleware systems, providing new opportunities for performance reflection and transparent adaptation.