📄 ch1.htm
字号:
<html>
<head>
<title>Chapter 1 -- Windows Communications Overview</title>
<meta NAME="GENERATOR" CONTENT="Microsoft FrontPage 3.0">
</head>
<body TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#CE2910">
<!-- Spidersoft WebZIP Ad Banner Insert -->
<!-- End of Spidersoft WebZIP Ad Banner Insert-->
<h1><font COLOR="#FF0000">Chapter 1</font></h1>
<h1><b><font SIZE="5" COLOR="#FF0000">Windows Communications Overview</font></b> </h1>
<hr WIDTH="100%">
<h3 ALIGN="CENTER"><font SIZE="+2" COLOR="#000000">CONTENTS<a NAME="CONTENTS"></a> </font></h3>
<ul>
<li><a HREF="#MAPIMessageServices">MAPI Message Services</a> </li>
<li><a HREF="#TAPITelephonyServices">TAPI Telephony Services</a> </li>
<li><a HREF="#SAPISpeechServices">SAPI Speech Services</a> </li>
<li><a HREF="#MCIMultimediaServices">MCI Multimedia Services</a> </li>
<li><a HREF="#ApplicationsCoveredinThisBook">Applications Covered in This Book</a> </li>
<li><a HREF="#DevelopmentTools">Development Tools</a> </li>
<li><a HREF="#HardwareandSoftwareTools">Hardware and Software Tools</a> </li>
<li><a HREF="#WhatsNotCoveredinThisBook">What's Not Covered in This Book</a> </li>
<li><a HREF="#HowtoUseThisBook">How to Use This Book</a> </li>
</ul>
<hr>
<p>This developer's guide is designed to show you how to design, develop, and deploy
applications that use messaging, telephony, and speech services available within the
Windows 95 operating system. The primary focus is on developing client-side applications.
Several chapters in this book cover the server-side aspects of these APIs, too. However,
the emphasis is on the client or desktop. </p>
<div align="center"><center>
<table BORDERCOLOR="#000000" BORDER="1" WIDTH="80%">
<tr>
<td><b>Note</b></td>
</tr>
<tr>
<td><blockquote>
<p>The primary focus of this book is Windows 95, and all examples are therefore in 32
bits. The same examples will work for Windows NT. The ideas can be applied to 16-bit
Win31, but no 16-bit examples are given in this book. </p>
</blockquote>
</td>
</tr>
</table>
</center></div>
<p>One book cannot begin to cover all the possible development tools and API sets that
provide message, telephony, and speech services for desktop pcs. The approach taken here
is to concentrate on the Microsoft API sets. This offers several advantages: First, by
using all Microsoft API models, the programmer gets to work with a consistent set of
interfaces that work well together. Second, there is no denying that Microsoft's presence
in the marketplace adds strength to any service model they develop. The time you invest in
learning a set of API calls to provide advanced Windows services is usually time well
spent. Using Microsoft API models assures you that your knowledge will not be useless in a
year or so when some other API model is abandoned due to lack of use. And third, the
Microsoft approach to service models is designed to allow third-party vendors to
contribute to the growth and development of the service model. This open approach means
you're really learning how to create programs that work with a variety of
hardware/software combinations and not tying your efforts to a single hardware or software
system. </p>
<h2><a NAME="MAPIMessageServices"><font SIZE="5" COLOR="#FF0000">MAPI Message Services</font></a></h2>
<p>The messaging system explored in this book is the Microsoft Messaging API (MAPI). The
MAPI system is one of the most widely used message models available for the pc
environment. While there are other message models in use today, they are not covered here
just because one book can't cover everything. If you are familiar with other message
models, your knowledge will help you gain a greater understanding of the MAPI system. </p>
<h2><a NAME="TAPITelephonyServices"><font SIZE="5" COLOR="#FF0000">TAPI Telephony Services</font></a></h2>
<p>The telephony model covered here is the Microsoft Telephony API (TAPI). Just as with
message services, there are competing telephony service models, too. The primary advantage
of TAPI to the programmer is that Microsoft has committed to providing the TAPI model as
part of the basic operating system for all future versions of Windows. For example, TAPI
is shipped as part of every Windows 95 operating system. Version 4.0 of Windows NT is also
designed to contain TAPI services as a fundamental part of the operating system. </p>
<p>Another major advantage of the TAPI model is that it is designed to work with multiple
hardware products. Programmers who use TAPI can be assured that their programs will work
the same from one installation to the next as long as TAPI-compliant hardware is used at
all locations. </p>
<h2><a NAME="SAPISpeechServices"><font SIZE="5" COLOR="#FF0000">SAPI Speech Services</font></a></h2>
<p>The speech service discussed here is Microsoft's Speech API (SAPI). There are several
vendor-specific speech APIs. As in the TAPI model, the real advantage of Microsoft's SAPI
is that it is designed to support multiple third-party vendor products. By writing to the
SAPI model, you can potentially increase the reach of your speech-enabled software to all
SAPI-compliant hardware. </p>
<h2><a NAME="MCIMultimediaServices"><font SIZE="5" COLOR="#FF0000">MCI Multimedia Services</font></a></h2>
<p>Some of the examples in this book also use the Microsoft Multimedia Communications
Interface (MCI) to add audio and video services. This is a well-established interface that
is supported by almost all existing audio and video hardware. </p>
<h2><a NAME="ApplicationsCoveredinThisBook"><font SIZE="5" COLOR="#FF0000">Applications
Covered in This Book</font></a></h2>
<p>The programming examples in this book move from simple, high-level examples and
progress to more complex, full-featured applications. Each section of the book has four
basic parts:
<ul>
<li><font COLOR="#000000">General theory</font> </li>
<li><font COLOR="#000000">Creating simple service-aware applications</font> </li>
<li><font COLOR="#000000">Building full-featured service implementation examples</font> </li>
<li><font COLOR="#000000">Designing applications that use the service in unique ways</font> </li>
</ul>
<p>Each section starts with the general theory of the API service. This includes coverage
of the general design of the service model and its objects, methods, and properties.
You'll also get information about the various developer tools available for building
programs that use the target service. </p>
<p>You'll then learn how to create service-aware applications. This usually involves
adding the target service to existing applications, such as adding <tt><font
FACE="Courier">Send</font></tt>, <tt><font FACE="Courier">Dial</font></tt>, or <tt><font
FACE="Courier">Speak</font></tt> buttons to a form. Service-aware applications use the
target service as an added feature instead of as a basic part of the program. You'll see
how you can add service features using high-level code routines. </p>
<p>The next level of programming examples shows you how to build applications that take
advantage of the target service as a basic part of the program design. Examples would be
an e-mail message reader, an online address book that can dial the selected address at the
push of a button, or a program that allows users to drag and drop text documents onto a
palette and then reads a selected document aloud. </p>
<p>Lastly, you'll learn how to create applications that use the service in unique ways.
For example, you could use the message service to send data between two programs running
on different machines on the same network, or use TAPI services to create an answering
machine application. </p>
<p>The final section of the book contains examples of applications that provide integrated
services: using MAPI and TAPI to build a dial-up FAX-back application; building a program
that allows users to dial in, request information from a database, and hear the results
spoken to them over the phone; and creating a single application that combines messaging,
telephony, and speech into a single voice-mail system. </p>
<p>While the examples in this book don't cover every possible use of the target APIs,
you'll find enough examples here to give you the techniques and skills you'll need to
build your own Windows applications to exploit the features of the MAPI, TAPI, and SAPI
services. </p>
<h2><a NAME="DevelopmentTools"><font SIZE="5" COLOR="#FF0000">Development Tools</font></a></h2>
<p>In the past, if you wanted to access advanced Windows services like MAPI, SAPI, and
TAPI, you had to use C or C++ developer tools. But now, with the introduction of OLE
libraries and the Microsoft OCX add-in control specification, Microsoft has made it
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -