home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
2_7.1
< prev
next >
Wrap
Text File
|
2001-01-27
|
4KB
|
87 lines
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<base href="http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/EZ30OZ00/2.7.1">
<title>
2.7.1 "OS/2 WARP and OpenDoc"
via IBM BookManager BookServer
</title>
</head>
<body background="/bookmgr/backdrop.gif">
<banner><br>
<a href="../../library"><img src="/bookmgr/libicon2.gif" border=0 alt="[Library]"></a>
<a href="CONTENTS#2.7.1"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="2.7"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.7.1.1"><img src="/bookmgr/next.gif" border=0 alt="[Next Topic]"></a>
<a href="../../search?book=EZ30OZ00"><img src="/bookmgr/search.gif" border=0 alt="[Search]" ></a>
<img src="/bookmgr/dslist.gif" border=0 alt="[Search Results]">
<img src="/bookmgr/dsprev.gif" border=0 alt="[Prev Topic Match]">
<img src="/bookmgr/dsnext.gif" border=0 alt="[Next Topic Match]">
<img src="/bookmgr/dnotes.gif" border=0 alt="[Notes]">
<img src="/bookmgr/dlnotes.gif" border=0 alt="[List Notes]">
<a href="../../print?book=EZ30OZ00"><img src="/bookmgr/print.gif" border=0 alt="[Print]"></a>
<a href="../../download/EZ30OZ00.boo"><img src="/bookmgr/download.gif" border=0 alt="[Download]" ></a>
<a href="../../help/book"><img src="/bookmgr/help.gif" border=0 alt="[Help]"></a>
<hr>
<a name="HDR4610DCA"><H3> 2.7.1 The Object Management Architecture</H3></a>
</banner>
<pre width="80">
The OMG, a consortium of object vendors is an important standardization
group with over 590 members. It is the only standardization group
defining standards for objects. They have been working since 1989 to
define an open object infrastructure. The architecture that was defined
by OMG is called Object Management Architecture (OMA) as shown in
<a href="#FIG4610D05">Figure 38</a>.
<p>
This chapter describes the basic architecture of the Object Request Broker
(CORBA), the Object Services, and the Common Facilities as shown in
<a href="#FIG4610D05">Figure 38</a>. CORBA is important for OpenDoc for the following reasons:
<p>
1. OpenDoc parts are CORBA-compliant objects.
<p>
2. OpenDoc itself has been adopted by the OMG as part of the CORBA
standard itself.
<p>
3. The services provided by CORBA give a good indication about what will
be in future versions of OpenDoc.
<p>
<p>
<a name="FIG4610D05"><hr>
</a>
<p>
<p>
<a href="picture-38?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P38.GIF" alt="PICTURE 38"></a>
<p>
<p>
<hr>
Figure 38. Object Management Architecture
<p>
The real heart of the CORBA architecture is the standardization of object
interfaces. The language by which this is done is called IDL, Interface
Definition Language. One of the reasons CORBA is so successful is the
fact that the OMG is defining all the services and interfaces by this IDL.
The IDL is a subset of C++ with some additional features. One example is
<a href="2.9.1#HDR4610DIP">"Sample IDL File Generated by Partmeister" in topic 2.9.1</a>. It supports
C++ pragmas and preprocessing. The OMG is separating clearly the
interfaces from the implementation. The OMG doesn't care about the
implementation. These are left to the vendors. This simplifies the
process to agree on standards.
<p>
Let's take a very short look at the whole architecture and see how OpenDoc
fits into this structure.
<p>
<p>Subtopics:
<ul>
<li> <a href="2.7.1.1"> 2.7.1.1 Object Request Broker</a>
<li> <a href="2.7.1.2"> 2.7.1.2 COSS Services</a>
</pre>
</ul>
<hr>
<br><a href="2.7"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.7.1.1"><img src="/bookmgr/next.gif" border=0 alt="[Next Topic]"></a>
<cite> ⌐ Copyright IBM Corp. 1996</cite>
<HR><p><h6><a href="/cgi-bin/bookmgr/library">IBM BookManager« BookServer</a> Copyright 1989, 1999<a href="http://www.ibm.com/"> IBM</a> Corporation. All rights reserved.</h6><p>
</BODY></HTML>