home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
2.7
< prev
next >
Wrap
Text File
|
2001-01-27
|
6KB
|
106 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">
<title>
2.7 "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"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="2.6.4"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.7.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="HDR4610DOM"><H2> 2.7 OpenDoc Object Model</H2></a>
</banner>
<pre width="80">
<p>
<a name="FIG4610D52"><hr>
</a>
<p>
<p>
<a href="picture-37?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P37.GIF" alt="PICTURE 37"></a>
<p>
<p>
<hr>
Figure 37. OpenDoc Object Management Services - System Object Model
<p>
<cite>If</cite> <cite>objects</cite> <cite>are</cite> <cite>to</cite> <cite>be</cite> <cite>assembled</cite> <cite>they</cite> <cite>must</cite> <cite>be</cite> <cite>compatible</cite> <cite>with</cite> <cite>one</cite> <cite>another.</cite>
<cite>This</cite> <cite>is</cite> <cite>rarely</cite> <cite>a</cite> <cite>problem</cite> <cite>when</cite> <cite>writing</cite> <cite>a</cite> <cite>single</cite> <cite>program,</cite> <cite>because</cite> <cite>all</cite> <cite>the</cite>
<cite>objects</cite> <cite>are</cite> <cite>written</cite> <cite>in</cite> <cite>the</cite> <cite>same</cite> <cite>language,</cite> <cite>run</cite> <cite>on</cite> <cite>the</cite> <cite>same</cite> <cite>machine,</cite> <cite>and</cite> <cite>use</cite>
<cite>the</cite> <cite>same</cite> <cite>operating</cite> <cite>system.</cite> <cite>But</cite> <cite>building</cite> <cite>entire</cite> <cite>information</cite> <cite>systems</cite> <cite>out</cite> <cite>of</cite>
<cite>objects</cite> <cite>is</cite> <cite>quite</cite> <cite>a</cite> <cite>different</cite> <cite>matter.</cite> <cite>Objects</cite> <cite>have</cite> <cite>to</cite> <cite>interact</cite> <cite>with</cite> <cite>each</cite>
<cite>other</cite> <cite>even</cite> <cite>if</cite> <cite>they</cite> <cite>are</cite> <cite>written</cite> <cite>in</cite> <cite>different</cite> <cite>languages,</cite> <cite>and</cite> <cite>run</cite> <cite>on</cite>
<cite>different</cite> <cite>hardware</cite> <cite>and</cite> <cite>software</cite> <cite>platforms.</cite>
<p>
<B>David</B> <B>Taylor,</B> <B>Business</B> <B>Engineering</B> <B>with</B> <B>Object</B> <B>Technology</B>
<p>
This chapter describes the basic architecture of the object model used by
OpenDoc. SOM System Object Model provides the underlying object model for
OpenDoc components.
<p>
SOM is the IBM implementation of the CORBA standard. CORBA stands for
Common Object Request Broker Architecture, which is defined by a
standardization group called Object Management Group. This group is
defining standards necessary for objects to interoperate. CORBA defines a
standard way of objects to communicate.
<p>
A component is an encapsulated building block which must be able to be
plugged in and out at run time. Components, or parts as they are called
in OpenDoc, can be developed independently by ISVs without knowing
anything from the other components. Object technology is a great
philosophy to provide the necessary encapsulation to minimize the
dependencies of components to the outside world. Part of the object
technology paradigm is to separate the definition of a component interface
from the implementation. A component technology must have a standardized
way of defining and describing interfaces and it must provide methods for
other components to discover their interfaces dynamically.
<p>
Therefore an object model must provide the following:
<p>
1. A standardized binary application interface to enable dynamic loading
and replacing of components very similar to the way DLLs are working.
<p>
2. An interface repository, which is available at run time to all
components. It provides the information and the methods to discover
the interfaces from other parts and objects at run time.
<p>
3. A standardized way to describe the interfaces.
<p>
<p>
There is a standard addressing all these requirements and defining all of
the infrastructure necessary for such a component technology. It was
defined by the Object Management Group.
<p>
<p>Subtopics:
<ul>
<li> <a href="2.7.1"> 2.7.1 The Object Management Architecture</a>
<li> <a href="2.7.2"> 2.7.2 Common Facilities</a>
<li> <a href="2.7.3"> 2.7.3 SOM</a>
<li> <a href="2.7.4"> 2.7.4 Distributed SOM</a>
<li> <a href="2.7.5"> 2.7.5 SOM and OpenDoc</a>
<li> <a href="2.7.6"> 2.7.6 Differences between SOM and COM</a>
<li> <a href="2.7.7"> 2.7.7 OpenDoc and SOM Summary and Outlook</a>
</pre>
</ul>
<hr>
<br><a href="2.6.4"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.7.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>