An Interoperable Object Reference (IOR) is a CORBA or RMI-IIOP reference that uniquely identified an object on a remote CORBA server.
IORs can be transmitted in binary over TCP/IP via the General Inter-ORB Protocol (the encoding may be big-endian or little-endian), or serialized into a string of hexadecimal digits (prefixed by the string IOR:) to facilitate transport by non-CORBA mechanisms such as HTTP, FTP, and e-mail.
The internal structure of an IOR may contain multiple components. Each component is identified by its integer code and has its own binary format. The codes are assigned by the Object Management Group. 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 ORB.
Famous quotes containing the words object and/or reference:
“Luxury, or a refinement on the pleasures and conveniences of life, had long been supposed the source of every corruption in government, and the immediate cause of faction, sedition, civil wars, and the total loss of liberty. It was, therefore, universally regarded as a vice, and was an object of declamation to all satyrists, and severe moralists.”
—David Hume (1711–1776)
“I think, for the rest of my life, I shall refrain from looking up things. It is the most ravenous time-snatcher I know. You pull one book from the shelf, which carries a hint or a reference that sends you posthaste to another book, and that to successive others. It is incredible, the number of books you hopefully open and disappointedly close, only to take down another with the same result.”
—Carolyn Wells (1862–1942)