(BQ) Part 2 book "Programming with C++" has contents: Implementation repo sitories and binding, C++ mapping for type any, type codes, type dynany, the omg naming service, multithreaded applications, performance, scalability, and maintainability,. and other contents. | IT-SC book: Advanced CORBA® Programming with C++ Part III: CORBA Mechanisms 527 IT-SC book: Advanced CORBA® Programming with C++ Chapter 13. GIOP, IIOP, and IORs Chapter Overview Even though CORBA goes to great lengths to shield applications from the details of networking, it is useful to have at least a basic understanding of what happens under the hood of an ORB. In this chapter, we present an overview of the General Inter-ORB Protocol (GIOP) and the Internet Inter-ORB Protocol (IIOP), and we explain how protocol-specific information is encoded in object references. Our treatment is by no means exhaustive. We show just enough of the protocols to give you a basic understanding of how CORBA achieves interoperability without losing extensibility. Unless you are building your own ORB, the precise protocol details are irrelevant. You can consult the CORBA specification [18] if you want to learn more. Sections to provide an overview of GIOP, including the requirements it makes on the underlying transport and its data encoding and message formats. Section then describes IIOP, which is a concrete realization of the abstract GIOP specification. Section shows how IORs encode information so that the protocols available for communication can be extended without affecting interoperability. Section outlines changes made to the protocols with the CORBA revision. An Overview of GIOP The CORBA specification defines the GIOP as its basic interoperability frame-work. GIOP is not a concrete protocol that can be used directly to communicate between ORBs. Instead, it describes how specific protocols can be created to fit within the GIOP framework. IIOP is one concrete realization of GIOP. The GIOP specification consists of the following major elements. Transport assumptions GIOP makes a number of assumptions about the underlying transport layer that carries GIOP protocol implementations. Common Data Representation (CDR) GIOP defines an .
