Corba Shopping
Request 		Website Links For
Common 		 

Information About

Corba
  CATEGORIES ABOUT COMMON OBJECT REQUEST BROKER ARCHITECTURE
   
corba
   
object-oriented programming
   
inter-process communication
   
software components
   
SHOPPER'S DELIGHT
 
Shop For:  
Department
Price Minimum:
Price Maximum:
      



In a general sense CORBA “wraps” code written in some language into a bundle containing additional information on the capabilities of the code inside, and how to call it. The resulting wrapped objects can then be called from other Program s (or CORBA Object s) over the Network . In this sense, CORBA can be considered as a Machine-readable documentation format, similar to a Header File but with considerably more information.

CORBA uses an Interface Definition Language (IDL) to specify the interfaces that objects will present to the world. CORBA then specifies a “mapping” from IDL to a specific implementation language like C++ or Java . This mapping precisely describes how the CORBA Data Type s are to be used in both client and server implementations. Standard mappings exist for Ada , C , C++ , Lisp , Smalltalk , Java , and Python . There are also non-standard mappings for Perl and Tcl implemented by ORBs written for those languages.

The CORBA IDL is only one example of an IDL.

This diagram illustrates how the generated code is used within the CORBA infrastructure:

This picture does not reflect all typically used possibilities. Normally the server side has the Portable Object Adapter that redirects calls either to the local Servants or (to balance the load) to the other servers. Also, both server and client parts frequently have interceptors that are described below.

In addition to providing users with a language and a platform-neutral Remote Procedure Call specification, CORBA defines commonly needed services such as transactions and security.


KEY FEATURES


Objects by Value (OBV)

Apart from remote objects, the CORBA and RMI-IIOP define the concept of the OBV. The code inside the methods of these objects is executed locally by default. If the OBV has been received from the remote side, the needed code must be either ''a priori'' known for both sides or dynamically downloaded from the sender. To make this possible, the record, defining OBV, contains the Code Base that is a space separated list of URL s from where this code should be downloaded. The OBV can also have the remote methods.

The OBV's may have fields that are transferred when the OBV is transferred. These fields can be OBVs themselves, forming the lists, trees or arbitrary graphs. The OBVs have the class hierarchy, including multiple inheritance and abstract classes.


CORBA Component Model (CCM)

CORBA Component Model (CCM) is an addition to the family of CORBA definitions. It was introduced with CORBA 3, and it describes standard application framework for CORBA components. It could be described as "language independent Enterprise Java Beans (EJB)".

The CCM has a component container, where software components can be installed. The container offers a set of services that the components can use. These services include (but are not limited to) authentication, persistence and transaction management. These are all the most used services a distributed system requires, and by moving the implementation of these services from the software components to the component container, the complexity of the components is dramatically reduced.


External links



Portable interceptors

Portable interceptors are the "hooks", used by CORBA and RMI-IIOP to mediate the most important functions of the CORBA system. CORBA standard defines the following types of interceptors:
# IOR interceptors mediate the creation of the new references to the remote objects, presented by the current server.
#Client interceptors usually mediate the remote method calls on the client (caller) side. If the object Servant (CORBA) exists on the same server where the method is invoked, they also mediate the local calls.
#Server interceptors mediate the handling of the remote method calls on the server (handler) side.

The interceptors can attach the specific information to the messages being sent and IORs being created. This information can be later read by the corresponding interceptor on the remote side. Interceptors can also throw forwarding exceptions, redirecting request to another target.


General InterORB Protocol (GIOP)

The GIOP is an abstract protocol by which Object Request Broker s (ORBs) communicate. Standards associated with the protocol are maintained by the Object Management Group (OMG).


Internet InterORB Protocol (IIOP)

The Internet Inter-Orb Protocol, is a Protocol for communication between CORBA ORBs that has been published by the Object Management Group. IIOP is an implementation of the GIOP for use over an Internet , and provides a mapping between GIOP messages and the TCP/IP layer.

SSLIOP is IIOP over SSL , providing Encryption and Authentication .


Network Data Delivery Service (NDDS)

The Network Data Delivery Service, NDDS emerged from Object Management Group (OMG) Data-Distribution Service (DDS) standard, provides a network middleware between application and operating system. Using the Publisher to relay the topic to all subscribers and simplifies the underlying low-level network with RTI standards-based API.

For Real-time applications, the traditional publish-subscribe model has some limitations. The Real-time applications need more deterministic timing control, reliability control, fault tolerance and thread awareness. Object Management Group (OMG) developed the CORBA and the DDS standards. DDS addresses publish-subscribe data distribution and extends publish-subscribe model for real-time systems. Based on DDS standard, Real-Time Innovations (RTI), Headquartered in the heart of Silicon Valley since 1991, products NDDS, the Real-Time Publish-Subscribe Network Middleware.

The Network Data Delivery Service (NDDS) is network messaging middleware that allows programmers to set up host-independent communication for distributed real-time applications. It implements the Publish-Subscribe communications model and runs on top of a standard internet UDP/IP protocol stack. NDDS supports for many architectures, Multi-OS, like Windows NT, 2000, XP / Linux / Solaris / VxWorks / Integrity / LynxOS and languages include C / C++ / Java.


CORBA LOCATION


CorbaLoc means Corba Location refers to a stringified object reference for a Corba object that looks similar to a URL.

All CORBA products must support two OMG-defined URLs: "corbaloc:" and "corbaname:". The purpose of these is to provide a human readable/editable way to specify a location where an IOR can be
obtained.

An example of corbaloc is shown below:

corbaloc::160.45.110.41:38693/StandardNS/NameServer-POA/_root

A CORBA product may optionally support the "http:", "ftp:" and "file:" formats. The semantics of these is that they provide details of how to download a stringified IOR (or, recursively,
download another URL that will eventually provide a stringified IOR).


External links