Common Object Request Broker Architecture: Difference between revisions

Revision as of 01:39, 4 October 2018

Revision as of 06:29, 7 October 2018

Line 34:

In order to build a system that uses or implements a CORBA-based distributed object interface, a developer must either obtain or write the IDL code that defines the object-oriented interface to the logic the system will use or implement. Typically, an ORB implementation includes a tool called an IDL compiler that translates the IDL interface into the target language for use in that part of the system. A traditional compiler then compiles the generated code to create the linkable-object files for use in the application. This diagram illustrates how the generated code is used within the CORBA infrastructure:

[[Image:orb.svg|center|thumb|Illustration of the autogeneration of the infrastructure code from an interface defined using the CORBA IDL]]

This figure illustrates the high-level paradigm for remote interprocess communications using CORBA. The CORBA specification further addresses data typing, exceptions, network protocols, communication timeouts, etc. For example: Normally the server side has the [[Portable Object Adapter]] (POA) that redirects calls either to the local [[Servant (CORBA)|servants]] or (to balance the load) to the other servers. The CORBA specification (and thus this figure) leaves various aspects of distributed system to the application to define including object lifetimes (although reference counting semantics are available to applications), redundancy/fail-over, memory management, dynamic load balancing, and application-oriented models such as the separation between display/data/control semantics (e.g. see [[Model–view–controller]]), etc.