Abstract

This article explains how CORBA binds requests to object implementations with the help of an implementation repository. The design of the implementation repository has profound influence on the flexibility, performance, scalability, and fault tolerance of an ORB, and we illustrate some of the trade-offs involved in various repository designs. Implementation repositories play an important role in building scalable object systems; we point out some issues that CORBA will need to address in the future to continue to scale and remain at the forefront of distributed object technology. One Repository to register them all, One Repository to find them, One Repository to start them all, and with IIOP bind them In the land of CORBA where the Objects lie.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.