Previous | Table of Contents | Next |
External communications between COM client machines, and between COM client machines and machines executing CORBA environments
and services, will follow specifications contained in CORBA.
Figure 17-7 on page 17-33 illustrates the required
distribution architecture. The following statements articulate the responsibilities of compliant solutions.
• All externalized CORBA object references will follow CORBA specifications for Interoperable Object References (IORs). Any IORs generated by components performing mapping functions must include a valid IIOP profile.
• The mechanisms for negotiating protocols and binding references to remote objects will follow the architectural model described in CORBA.
• A product component acting as a CORBA client may bind to an object by using any profile contained in the object’s IOR. The client must, however, be capable of binding with an IIOP profile.
• Any components that implement CORBA interfaces for remote use must support the IIOP.
17.9 Interworking Targets
This specification is targeted specifically at interworking between the following systems and versions:
• CORBA as described in CORBA: Common Object Request Broker Architecture and Specification.
• OLE as embodied in version 2.03 of the OLE run-time libraries.
• Microsoft Object Description Language (ODL) as supported by MKTYPELIB version 2.03.3023.
• Microsoft Interface Description Language (MIDL) as supported by the MIDL Compiler version 2.00.0102.
In determining which features of Automation to support, the expected usage model for Automation Views follows the Automation
controller behavior established by Visual Basic 4.0.