Hispanopedia Wiki
Articulo de referencia

General Inter-ORB Protocol

In distributed computing , General Inter-ORB Protocol ( GIOP ) is the message protocol by which object request brokers (ORBs) communicate in CORBA . Standards associated with th...

Hispanopedia WikiContenido en espanolLectura gratuita

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[1] (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.[2]
  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 InterORB Protocol (ZIOP) — A zipped version of GIOP that reduces the bandwidth usage

Environment Specific Inter-ORB Protocols

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).[3][4]

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).[3][5]:48[4] DCE-CIOP is defined in chapter 16 of the CORBA 2.6.1 standard.[1]

Messages

The General Inter-ORB Protocol (GIOP) is the message protocol used by object request brokers (ORBs) to communicate in CORBA-based distributed computing systems. GIOP 2.0.2 is the current version of this protocol, and it provides a number of concrete protocols such as IIOP, SSLIOP, HTIOP, and ZIOP. IIOP is a mapping of GIOP messages to the TCP/IP layer for use over the Internet, while SSLIOP provides encryption and authentication. HTIOP, on the other hand, enables transparent proxy bypassing by using IIOP over HTTP. Finally, ZIOP is a compressed version of GIOP that minimizes bandwidth usage. In addition to these protocols, CORBA also includes the concept of an Environment Specific Inter-ORB Protocol (ESIOP) to address specific requirements. An ESIOP can use an alternative protocol encoding to improve efficiency over networks with limited bandwidth or high latency, or can be used to layer CORBA on top of non-CORBA technologies such as DCE. DCE Common Inter-ORB Protocol (DCE-CIOP) is an ESIOP that maps CORBA to DCE RPC and CDR.[6]

Further reading

  • "The official CORBA standard from the OMG group". Archived from the original on 2017-04-02. Retrieved 2016-03-03.

See also

References

  1. 12"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).
  2. ↑"IIOP: OMG's Internet Inter-ORB Protocol: A Brief Description". Archived from the original on 2014-06-28. Retrieved 2014-08-19.
  3. 12Linda 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.
  4. 12Zahir Tari; Omran Bukhres (7 April 2004). Fundamentals of Distributed Object Systems: The CORBA Perspective. John Wiley & Sons. p. 178. ISBN 978-0-471-46411-2ESIOP (Environment Specific Inter-ORB Protocol) es un protocolo GIOP concreto que se utiliza para comunicarse en un entorno particular. ESIOP está optimizado para un entorno específico y puede elegirse en lugar de TCP/IP. Un ejemplo de ESIOP es DCE-CIOP (DCE-Common Inter-ORB Protocol), que utiliza un subconjunto de las funcionalidades de DCE-RPC y partes de la especificación GIOP.
  5. ↑ Kim, Dong Jin; Namgoong, Han; Lew, Young-Chul (5 de diciembre de 1997). Danthine, Andre; Diot, Christophe (eds.). Un puente para la comunicación heterogénea entre CORBA y DCE . De los servicios multimedia a los servicios de red: 4.º Taller Internacional COST 237, Lisboa, Portugal, 15-19 de diciembre de 1997. Actas. Springer. págs. 45-58 . ISBN  978-3-540-63935-0El otro enfoque consiste en utilizar el Protocolo Inter-ORB Específico del Entorno (ESIOP), el Protocolo Inter -ORB Común de DCE (DCE-CIOP). Los mensajes DCE-CIOP representan tipos IDL de OMG mediante la sintaxis de transferencia de Representación de Datos Comunes (CDR).
  6. ↑ "Acerca de la especificación de la arquitectura del agente de solicitudes de objetos comunes, versión 3.4" . www.omg.org . Consultado el 13 de abril de 2023 .