General Inter-ORB Protocol

From Wikipedia, the free encyclopedia
Jump to: navigation, search

In distributed computing, General Inter-ORB Protocol (GIOP) is the message protocol by which object request brokers (ORBs) communicate in CORBA. Standards associated with the protocol are maintained by the Object Management Group (OMG). The current version of GIOP is 2.0.2. The GIOP architecture provides several concrete protocols, including:

  1. Internet InterORB Protocol (IIOP) — The Internet Inter-Orb Protocol is an implementation of the GIOP for use over the Internet, and provides a mapping between GIOP messages and the TCP/IP layer.[1]
  2. SSL InterORB Protocol (SSLIOP) — SSLIOP is IIOP over SSL, providing encryption and authentication.
  3. HyperText InterORB Protocol (HTIOP) — HTIOP is IIOP over HTTP, providing transparent proxy bypassing.
  4. Zipped IOP (ZIOP) — A zipped version of GIOP that reduces the bandwidth usage

Environment Specific Inter-ORB Protocols[edit]

As an alternative to GIOP, CORBA includes the concept of an Environment Specific Inter-ORB Protocol (ESIOP). While GIOP is defined to meet general-purpose needs of most CORBA implementations, an ESIOP attempts to address special requirements. For example, an ESIOP might use an alternative protocol encoding to improve efficiency over networks with limited bandwidth or high latency. ESIOPs can also be used to layer CORBA on top of some non-CORBA technology stack, such as Distributed Computing Environment (DCE).[2][3]

DCE Common Inter-ORB Protocol (DCE-CIOP) is an ESIOP for use in DCE. It maps CORBA to DCE RPC and CDR (Command Data Representation).[2][4]:48[3] DCE-CIOP is defined in chapter 16 of the CORBA 2.6.1 standard.[5]

Messages[edit]

Further reading[edit]

References[edit]

  1. ^ http://www.omg.org/library/iiop4.html
  2. ^ a b Linda Rising (23 July 2001). Design Patterns in Communications Software. Cambridge University Press. p. 445. ISBN 978-0-521-79040-6. In addition to the standard GIOP and IIOP protocols, the CORBA specification allows ORB implementors to define Environment Specific Inter-ORB Protocols (ESIOP)s... Only one ESIOP protocol is defined in the CORBA 2.x family of specifications: the DCE Common Inter-ORB Protocol (DCE-CIOP). The OMG is attempting to standardize other protocols for such domains, such as wireless and mobile systems, which have unique performance characteristics and optimization points. 
  3. ^ a b Zahir Tari; Omran Bukhres (7 April 2004). Fundamentals of Distributed Object Systems: The CORBA Perspective. John Wiley & Sons. p. 178. ISBN 978-0-471-46411-2. ESIOP (Environment Specific Inter-ORB Protocol) is a concrete GIOP protocol which is used to communicate in a particular environment. An ESIOP is optimized for a specific environment and may be chosen over TCP/IP... An example of ESIOP is DCE-CIOP (DCE-Common Inter-ORB Protocol) which makes use of a subset of DCE-RPC facilities and parts of GIOP specification. 
  4. ^ Kim, Dong Jin; Namgoong, Han; Lew, Young-Chul (5 December 1997). Danthine, Andre; Diot, Christophe, eds. A bridge for heterogeneous communication between CORBA and DCE. From Multimedia Services to Network Services: 4th International COST 237 Workshop, Lisboa, Portugal, December 15-19, 1997. Proceedings. Springer. p. 45–58. ISBN 978-3-540-63935-0. The other approach is using Environment Specific Inter-ORB Protocol(ESIOP), the DCE Common Inter-ORB Protocol(DCE-CIOP). DCE-CIOP messages represent OMG IDL types by using the Common Data Representation(CDR) transfer syntax. 
  5. ^ "The DCE ESIOP". The Common Object Request Broker: Architecture and Specification: Revision 2.6.1 (PDF). OMG. May 2002. p. 557. Retrieved 2016-05-11. This chapter specifies an Environment-Specific Inter-ORB Protocol (ESIOP) for the OSF DCE environment, the DCE Common Inter-ORB Protocol (DCE-CIOP).