From Wikipedia, the free encyclopedia
Jump to navigation
Jump to search
|
|
| Line 1: |
Line 1: |
| {{Unreferenced|date=December 2009}}
| | #REDIRECT [[Common Object Request Broker Architecture#Features]] |
| An '''Interoperable Object Reference''' ('''IOR''') is a [[CORBA]] or [[RMI-IIOP]] [[Reference (computer science)|reference]] that uniquely identifies an [[object (computer science)|object]] on a remote CORBA [[Server (computing)|server]].
| |
|
| |
|
| IORs can be transmitted in binary over [[TCP/IP]] via the [[General Inter-ORB Protocol]] (the encoding may be [[endianness|big-endian or little-endian]]), or serialized into a string of hexadecimal digits (prefixed by the string ''<code>IOR:</code>'') to facilitate transport by non-CORBA mechanisms such as [[HTTP]], [[File Transfer Protocol|FTP]], and [[e-mail]].
| | {{Rcat shell| |
| | | {{R to related topic}} |
| The internal structure of an IOR may contain multiple components. Each component is identified by its integer code and has its binary format. [[Object Management Group]] assigns the codes. The typical IOR normally contains:
| | }} |
| | |
| * the IP address of the remote host,
| |
| * the number of the remote port on that the CORBA server is listening,
| |
| * a string defining the class of the remote object on which the methods will be invoked, and
| |
| * the object key that is used by the server ORB to identify the object.
| |
| | |
| It is possible to register special objects (IOR interceptors) that can add the needed specific components to the IOR being created by the particular [[Object Request Broker|ORB]].
| |
| | |
| [[Category:Common Object Request Broker Architecture]]
| |
| | |
| {{Compu-network-stub}}
| |
Latest revision as of 05:23, 28 December 2025