Previous page Next page Bottom Top One level up Home

CORBA

Webpages concerning "CORBA"

BenchieRanking
Open CORBA benchmarking
Details + Preview
http://nenya.ms.mff.cuni.cz/~bench/
Keywords:
CORBA, benchmark, benchmarking, testing

http://nenya.ms.mff.cuni.cz/~bench/

Christof.Meerwald@freeorbwatch.progRanking
Free-ORB Watch: Overview of free Java & C++ ORBs.
Details + Preview
http://cmeerw.org/freeorbwatch/

http://cmeerw.org/freeorbwatch/

Object Management GroupRanking
Details + Preview
http://www.omg.org/
Keywords:
UML, MDA, Certification, CORBA, OMG, Meetings, IDL, XML, Technology, Middleware, Webcast

http://www.omg.org/

CORBA & CORBA Component Model (CCM)Ranking
Details + Preview
http://www.ditec.um.es/~dsevilla/ccm/

http://www.ditec.um.es/~dsevilla/ccm/

CORBA Product ProfilesRanking
Details + Preview
http://www.puder.org/corba/matrix/

http://www.puder.org/corba/matrix/

Linux DCE, CORBA and DCOM GuideRanking
A listing and evaluation of Linux Distributed Computing packages, focusing on CORBA features, examples and performance.
Details + Preview
http://linas.org/linux/corba.html
Keywords:
Linux, CORBA, DCE, DCOM, RPC, evaluation, performance, example

http://linas.org/linux/corba.html

Real-Time and Embedded CORBARanking
Details + Preview
http://www.realtime-corba.com/

http://www.realtime-corba.com/

Common Object Request Broker ArchitectureRanking
Details + Preview
http://www.sei.cmu.edu/str/descriptions/corba.html

http://www.sei.cmu.edu/str/descriptions/corba.html

Help building the largest human-edited directory of the web
Suggest URL - Open Directory Project - Become an editor
directopedia.org uses links and structure from dmoz Open Directory Project.
The contents has been generating using technology developed by scientec.

Wikipedia-Article "CORBA"

In computing, Common Object Request Broker Architecture (CORBA) is a standard for software componentry, created and controlled by the Object Management Group (OMG). It defines APIs, communication protocol, and object/service information models to enable heterogeneous applications written in various languages running on various platforms to interoperate. CORBA therefore provides platform and location transparency for sharing well-defined objects across a distributed computing platform.

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 programs (or CORBA objects) 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 types 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.

Contents

[edit]

Key Features

[edit]

Objects by Value (OBV)

Apart 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 URLs 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.

[edit]

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, persistance 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.

[edit]

External links

[edit]

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:

  1. IOR interceptors mediate the creation of the new references to the remote objects, presented by the current server.
  2. 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.
  3. 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.

[edit]

General InterORB Protocol (GIOP)

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

[edit]

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.

[edit]

External links

[edit]

CORBA implementations

[edit]

See also

Wikibooks
Wikibooks Programming has more about this subject:
[edit]

References

[edit]

External links

This article is based on the article "CORBA" from Wikipedia - the free encyclopedia created and edited by online user community. This article is distributed under the terms of GNU Free Documentation License. Here you find the list of authors of this article. The article can only edited within Wikipedia. Edit this article in Wikipedia.