📄 ch13.htm
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<SCRIPT LANGUAGE="JavaScript">
<!--
function popUp(pPage) {
var fullURL = document.location;
var textURL = fullURL.toString();
var URLlen = textURL.length;
var lenMinusPage = textURL.lastIndexOf("/");
lenMinusPage += 1;
var fullPath = textURL.substring(0,lenMinusPage);
popUpWin = new Object() ;
figDoc= popUpWin.document;
zhtm= '<HTML><HEAD><TITLE>' + pPage + '</TITLE>';
zhtm += '</HEAD>';
zhtm += '<BODY bgcolor="#FFFFFF">';
zhtm += '<IMG SRC="' + fullPath + pPage + '">';
zhtm += '<P><B>' + pPage + '</B>';
zhtm += '</BODY></HTML>';
window.popUpWin.document.write(zhtm);
window.popUpWin.document.close();
// Johnny Jackson 4/28/98
}
//-->
</SCRIPT>
<META NAME="Author" Content="Steph Mineart">
<TITLE>Managing Multivendor Networks -- Ch 13 -- Software Considerations</TITLE>
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF">
<!--#exec cmd="/www/docs/ssi-bin/restricted_search.ssi"-->
<!--#exec cmd="/www/docs/ssi-bin/inc.ssi"-->
<CENTER>
<H1><IMG SRC="que.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/que.gif" WIDTH="171" HEIGHT="66" ALIGN="BOTTOM" BORDER="0"><BR>
<FONT COLOR="#000077">Managing Multivendor Networks</FONT></H1>
</CENTER>
<CENTER>
<P><A HREF="ch12.htm" tppabs="http://docs.rinet.ru:8080/MuNet/ch12/ch12.htm"><IMG SRC="previous.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/previous.gif" WIDTH="128" HEIGHT="28"
ALIGN="BOTTOM" ALT="Previous chapter" BORDER="0"></A><A HREF="apa.htm" tppabs="http://docs.rinet.ru:8080/MuNet/apa/apa.htm"><IMG
SRC="next.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/next.gif" WIDTH="128" HEIGHT="28" ALIGN="BOTTOM" ALT="Next chapter"
BORDER="0"></A><A HREF="index-2.htm" tppabs="http://docs.rinet.ru:8080/MuNet/index.htm"><IMG SRC="contents.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/contents.gif" WIDTH="128"
HEIGHT="28" ALIGN="BOTTOM" ALT="Contents" BORDER="0"></A>
<HR>
</CENTER>
<CENTER>
<H1><FONT COLOR="#000077">- 13 -<BR>
Software Considerations</FONT></H1>
</CENTER>
<UL>
<LI><A HREF="#Heading1">WinSock</A>
<LI><A HREF="#Heading2">Macintosh File Sharing</A>
<LI><A HREF="#Heading3">Component Technology</A>
<UL>
<LI><A HREF="#Heading4">OLE</A>
<LI><A HREF="#Heading5">CORBA</A>
<LI><A HREF="#Heading6">OpenDoc</A>
<LI><A HREF="#Heading7">DCE</A>
</UL>
<LI><A HREF="#Heading8">Data Warehouses and Repositories</A>
<LI><A HREF="#Heading9">World Wide Web</A>
</UL>
<P>
<HR SIZE="4">
</P>
<P>The advent of multivendor networks and client/server architectures has resulted
in more software being cross-platform in nature. Cross-platform software development
is simple for programs without a GUI; a simple recompile of a C program will do the
job. It is more complicated for programs with a graphical front-end, but end users
now expect this front-end from developers. Fortunately, there are several development
tools available for this purpose. These include:
<UL>
<LI><I>Uniface 6 (Uniface Corp.).</I> Uniface can be used to create a generic interface,
which is defined in an object repository instead of in code.<BR>
<BR>
<LI><I>Zapp Developer's Suite (Inmark Development Corp.).</I> This suite is actually
an application framework, which includes a set of C++ class libraries with prebuilt
services. Screens can be designed by dragging and dropping interface objects, and
the resulting C++ code that is automatically generated can be compiled for either
UNIX or Windows.<BR>
<BR>
<LI><I>UIM/X (Bluestone Communications, Inc.).</I> UIM/X is an object-oriented development
tool. It uses native libraries to create a more compliant look and feel, and has
an interactive GUI builder. The UIM/X Cross Platform Toolset provides developers
with a set of cross-platform interface components.
</UL>
<H2><A NAME="Heading1"></A><FONT COLOR="#000077">WinSock</FONT></H2>
<P><I>WinSock (Windows Sockets)</I> is an open API designed by Microsoft that provides
the means of using TCP/IP with Windows. The newest version, WinSock 2, will add support
for IPX/SPX, DECnet, and OSI. WinSock 2 is transport independent, and includes a
complete set of APIs for programming to multiple network transports concurrently.
(In addition, WinSock 2 will permit applications to take advantage of high-speed
ATM switching technology. The API will permit existing applications to be adapted
to ATM with only a minimal amount of reprogramming.)
<BLOCKQUOTE>
<P>
<HR>
<FONT COLOR="#000077"><B>The OAG and Multivendor Application Integration</B></FONT><BR>
The Open Applications Group (OAG) has demonstrated a specification for multivendor
application integration. Two members of the consortium plan to deliver systems with
snap-together functionality by next year. The OAG specification will enable client/server
applications to be integrated "out of the box," without having to add on
extra software interfaces. The applications will pass data directly between one another
in a common format. Compliant applications will contain an API written to the OAG
message format specification, known as the Business Document Exchange. If widely
accepted, applications written to this specification will be capable of recognizing
each other's data.
<HR>
</BLOCKQUOTE>
<H2><A NAME="Heading2"></A><FONT COLOR="#000077">Macintosh File Sharing</FONT></H2>
<P>The Macintosh is not widely used in corporate networks, although it does have
its niche areas, such as graphics and multimedia. Several utilities are available
to enable PCs to recognize Macintosh files. TCP/IP ships with the Macintosh hardware
and is actually simple to configure on the Apple Macintosh platform. Any TCP/IP application
can work with the Macintosh TCP/IP drivers.</P>
<P>AppleTalk is the Macintosh's native network protocol, although TCP/IP might actually
be simpler. Some network managers prefer to avoid AppleTalk on the corporate net,
despite the fact that there is actually little justification for this. Although AppleTalk
uses a small packet size, this does not necessarily mean it will generate more traffic.
AppleTalk does generate, however, some additional traffic because of the automation
inherent in the protocol. Devices communicate with each other over the AppleTalk
network in order to make AppleTalk a plug-and-play network; it is not necessary to
have to type in addresses and setup data for each device. TCP/IP is moving more toward
this model with <I>Dynamic Host Configuration Protocol (DHCP),</I> which is very
similar to the <I>AppleTalk Address Resolution Protocol (AARP).</I></P>
<P>Tools such as Wall Data Inc.'s <I>RUMBA</I> enable the Mac to participate in IBM-based
networks. With this tool, Mac users can communicate with IBM mainframes and minicomputers,
and with other platforms. Mac RUMBA client software integrates Wall Data's (Kirkland,
Washington) SNA*ps mainframe gateway technology with the company's RUMBA PC-to-mainframe
client software.
<H2><A NAME="Heading3"></A><FONT COLOR="#000077">Component Technology</FONT></H2>
<P>The concept of distributed objects holds great potential. A distributed object
is a software component that performs functions for other objects. They can be distributed
throughout the network and accessed by any network user with authorization, and the
objects can be assembled into complete distributed applications.</P>
<P>There are four separate, and sometimes conflicting, standards for distributed
objects: OLE, CORBA, DCE, and OpenDoc. These standards offer a way for different
objects to communicate, regardless of vendor origin, and bring developers a higher
level of abstraction. Instead of focusing on clients and servers, the developer works
with users, objects, and methods. It is no longer necessary to track which server
process is executing each function because this information is encapsulated within
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -