x x x x x x x x x x x x x x x x CORBA, like any technology or standard, has had to continually evolve since its original publication in order to remain viable as a basis for distributed applications. For example, the initial version of CORBA did not specify a standard protocol that applications could use to communicate with each other. For early CORBA users, the fact that each ORB used its own proprietary communication protocols did not present a problem. This was because most CORBA applications using version 1.0 were small enough that each could rely on the services of only a single ORB. However, as applications became larger and more distributed, they eventually needed to interact with other applications built using a different ORB. As a result, the standard General Inter-ORB Protocol (GIOP) and its specification for implementation over TCP/IP, the Internet Inter-ORB Protocol (IIOP), were added to version 2.0 of the CORBA specification, which was published in 1995. Such enhancements and modifications of the CORBA specification over the years have increased its usefulness and applicability to an ever-growing variety of distributed computing problems.
No takes yet. Share an insight, caveat, or question.
Steve Vinoski (1998) studied this question.
Synapse has enriched one closely related paper. Consider it for comparative context: