Object Request Broker


Also found in: Dictionary, Thesaurus, Medical, Acronyms, Wikipedia.
Related to Object Request Broker: Corba

object request broker

[′äb·jikt ri¦kwest ‚brō·kər]
(computer science)
The central component of CORBA, which passes requests from clients to the objects on which they are invoked. Abbreviated ORB.

Object Request Broker

(programming)
(ORB) Part of the OMG CORBA specification, an ORB's basic function is to pass method invocation requests to the correct objects and return the results to the caller.

To achieve this the ORB must be able must be able to identify and locate objects, handle connections from invoker and the data returned from methods. Communication between the ORB and applications are achieved through IDL stubs and skeletons whilst the OMG has specified IIOP as the protocol through which ORBs may communicate with each other. Using IIOP, an ORB may request method invocations from a remote object.

ORB

(Object Request Broker) Software that handles the communication of messages from the requesting program (client) to the object as well as any return values from the object back to the calling program. See CORBA and DCOM. See also ORB disk.
References in periodicals archive ?
The Common Object Request Broker: Architecture and Specification.
Hitachi Europe Ltd and OpenTrade Technologies Ltd have signed a partnership agreement to integrate Hitachi's object-oriented transaction processing manager known as TPBroker with OpenTrade's Real-time Middleware Solution to produce the first real-time implementation of an Object Request Broker.
SilverStream Inc has gone to San Jose, California-based ObjectEra Inc for object request broker technology to use within version 3.0 of the SilverStream Enterprise Application Server.
We have built a prototype intrusion detection system (IDS) to protect applications [6] that are based on the Common Object Request Broker Architecture (CORBA), which is promulgated by the Object Management Group (OMG) [8].
ICL is to licence its object request broker software, DAIS, to Peerlogic, which will have exclusive source code rights to all DAIS products.
Dunstan Thomas will provide a dedicated team of around 25 professionals to provide consulting, development and training on projects involving Inprise's Application Server, VisiBroker Object Request Broker, AppCenter and development tools, including Borland's JBuilder, C++Builder and Delphi.
The ability to move code from the service to its client is the core difference between the Jini environment and other distributed systems, such as the Common Object Request Broker Architecture (CORBA) [4] and the Distributed Common Object Model (DCOM) [5].
While the company publicly announced the immediate availability of a Linux version of its Visibroker object request broker (ORB) on August 10, and also demonstrated a Linux version of its JBuilder Java integrated development environment (IDE), there was no news of a Delphi for Linux at that time.
Guest editor Krishnan Seetharaman, a principal software engineer at General DataComm, piloted this section into a fine compilation of pieces that reflect the most recent version of CORBA, its design properties, new apps, along with a comprehensive look at the Object Management Architecture, and the Object Request Broker. We thank these authors for helping to connect the many CORBA components for us.
According to Soken's "Distributed Object Computing in Japan: 1999 Market and Trends", the Object Management Group's Common Object Request Broker Architecture is now the preferred choice for large scale, multi-platform integration projects at 61% of Japanese companies.
The Common Object Request Broker Architecture (CORBA) [1] is a conceptual "software bus that allows applications to communicate with one another, regardless of who designed them, the platform they are running on, the language they are written in, and where they are executing.
When this interoperability goal was realized in 1996 with the issuance of the CORBA 2.0 (Common Object Request Broker Architecture 2.0) specification [2, 6], two notable things happened: First, the infrastructure-oriented OMG members who had been concentrating on CORBA and the basic services were suddenly free to expand their horizons to include extended features; as a result, the basic CORBA object model is being extended to include multiple interfaces per object, objects passable by value, a beans-like component model, and support for realtime, fault-tolerant, and embedded CORBA [3].

Full browser ?