Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
General Inter-ORB Protocol
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Protocol by which object request brokers communicate in CORBA}} {{refimprove|date=September 2014}} In [[distributed computing]], '''General Inter-ORB Protocol''' ('''GIOP''') is the message [[communications protocol|protocol]] by which [[object request broker]]s (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: # Internet InterORB Protocol<ref name=":0" /> (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 [[Internet protocol suite|TCP/IP]] layer.<ref>{{cite web |url=http://www.omg.org/library/iiop4.html |title=IIOP: OMG's Internet Inter-ORB Protocol: A Brief Description |accessdate=2014-08-19 |url-status=dead |archiveurl=https://web.archive.org/web/20140628185045/http://www.omg.org/library/iiop4.html |archivedate=2014-06-28 }}</ref> # SSL InterORB Protocol (SSLIOP) — SSLIOP is IIOP over [[Secure Sockets Layer|SSL]], providing [[encryption]] and [[authentication]]. # HyperText InterORB Protocol (HTIOP) — HTIOP is IIOP over [[HTTP]], providing transparent proxy bypassing. # 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).<ref name="Rising2001">{{cite book|author=Linda Rising|title=Design Patterns in Communications Software|url=https://books.google.com/books?id=vy1Zj1OOUUwC&pg=PA445|date=23 July 2001|publisher=Cambridge University Press|isbn=978-0-521-79040-6|page=445|quote=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.}}</ref><ref name="TariBukhres2004">{{cite book|author1=Zahir Tari|author2=Omran Bukhres|title=Fundamentals of Distributed Object Systems: The CORBA Perspective|url=https://books.google.com/books?id=4mZNmR-a3jwC&pg=PA178|date=7 April 2004|publisher=John Wiley & Sons|isbn=978-0-471-46411-2|page=178|quote=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.}}</ref> 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).<ref name="Rising2001" /><ref name="KimNamgoongLew1997">{{cite conference |last1=Kim |first1=Dong Jin |last2=Namgoong |first2=Han |last3=Lew |first3=Young-Chul |title=A bridge for heterogeneous communication between CORBA and DCE |conference=From Multimedia Services to Network Services: 4th International COST 237 Workshop, Lisboa, Portugal, December 15-19, 1997. Proceedings |editor-last=Danthine |editor-first=Andre |editor2-last=Diot |editor2-first=Christophe |publisher=Springer |date=5 December 1997 |page= |pages=45β58 |isbn=978-3-540-63935-0 |url=https://books.google.com/books?id=3-E7lIWgF8kC&pg=PA48 |quote= 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.}}</ref>{{rp|48}}<ref name="TariBukhres2004" /> DCE-CIOP is defined in chapter 16 of the CORBA 2.6.1 standard.<ref name=":0">{{cite book |url=http://www.omg.org/cgi-bin/doc?formal/2002-05-15.pdf |title=The Common Object Request Broker: Architecture and Specification: Revision 2.6.1 |chapter=The DCE ESIOP |publisher=[[Object Management Group|OMG]] |date=May 2002 |page=557 |accessdate=2016-05-11 |quote=This chapter specifies an Environment-Specific Inter-ORB Protocol (ESIOP) for the OSF DCE environment, the DCE Common Inter-ORB Protocol (DCE-CIOP). }}</ref> ==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, [https://docs.oracle.com/cd/E19146-01/index.html 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.<ref>{{Cite web |title=About the Common Object Request Broker Architecture Specification Version 3.4 |url=https://www.omg.org/spec/CORBA/ |access-date=2023-04-13 |website=www.omg.org}}</ref> ==Further reading== *{{cite web |url=http://www.omg.org/spec/CORBA/Current/ |title=The official CORBA standard from the OMG group |access-date=2016-03-03 |archive-url=https://web.archive.org/web/20170402202151/http://www.omg.org/spec/CORBA/Current/ |archive-date=2017-04-02 |url-status=dead }} ==See also== *[[DIIOP]] ==References== {{Reflist}} [[Category:Distributed computing]] {{compu-network-stub}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Cite book
(
edit
)
Template:Cite conference
(
edit
)
Template:Cite web
(
edit
)
Template:Compu-network-stub
(
edit
)
Template:Refimprove
(
edit
)
Template:Reflist
(
edit
)
Template:Rp
(
edit
)
Template:Short description
(
edit
)