The annotated C++ reference manual
The annotated C++ reference manual
Design of Dynamically Reconfigurable Real-Time Software Using Port-Based Objects
IEEE Transactions on Software Engineering
Proceedings of the seventeenth ACM symposium on Operating systems principles
Foundations of component-based systems
Foundations of component-based systems
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
A CORBA Compliant Real-Time Multimedia Platform for Broadband Networks
TreDS '96 Proceedings of the International Workshop on Trends in Distributed Systems: CORBA and Beyond
Specifying QoS for Multimedia Communications within Distributed Programming Environments
Proceedings of the Third International COST 237 Workshop on Multimedia Telecommunications and Applications
Dynamically Reconfigurable Embedded Software - Does It Make Sense?
ICECCS '96 Proceedings of the 2nd IEEE International Conference on Engineering of Complex Computer Systems
Middleware '98 Proceedings of the IFIP International Conference on Distributed Systems Platforms and Open Distributed Processing
| Hi-index | 0.00 |
This paper introduces the concept of "interaction points" which are currently used in an experimental programming environment, the In-process Modular Programming (IMP) platform. IMP is a Microsoft COM-style platform designed specifically for building component-based applications in real-time and embedded environments, and used for research prototyping at Lucent Technologies, Bell-labs. Interaction points serve as a unified abstraction for a wide range of inter-component communication mechanisms. They allow the programmer to easily take advantage of available operating system level mechanisms such as semaphores, shared memory, spinlocks and I/O buffers, in order to realise advanced inter-component communication paradigms. They excel in supporting broadcast and multicast communication, which are often difficult to realise with point-to-point communications such as those provided by conventional program function calls. In addition to supporting operating system mechanisms, interaction points also provide a mechanism for building re-useable custom communication facilities that are not themselves, considered worthy of componentisation. Finally, the use of interaction points helps to maintain an explicit definition of communications on component-interfaces and thus avoid problems of ill specified 'hidden' component interactions that often lead to problems during third party re-use.