📄 ch13.htm
字号:
<html>
<head>
<title>Chapter 13 -- Part II Summary-The Messaging API</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 13</font></h1>
<h1><b><font SIZE="5" COLOR="#FF0000">Part II Summary-The Messaging API</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="#Chapter3WhatIsMAPI">Chapter 3, "What Is MAPI?"</a> </li>
<li><a HREF="#Chapter4MAPIArchitecture">Chapter 4, "MAPI Architecture"</a> </li>
<li><a HREF="#Chapter5UsingtheMicrosoftExchange">Chapter 5, "Using the Microsoft
Exchange Forms Designer"</a> </li>
<li><a HREF="#Chapter6CreatingMAPIAwareApplicat">Chapter 6, "Creating MAPI-Aware
Applications"</a> </li>
<li><a HREF="#Chapter7CreatingaSimpleMAPI">Chapter 7, "Creating a Simple MAPI Client
with the MAPI Controls"</a> </li>
<li><a HREF="#Chapter8TheOLEMessagingLibrary">Chapter 8, "The OLE Messaging
Library"</a> </li>
<li><a HREF="#Chapter9CreatingaMAPIMailingList">Chapter 9, "Creating a MAPI Mailing
List Manager with the OLE Messaging Library"</a> </li>
<li><a HREF="#Chapter10BuildingaMAPIEnabled">Chapter 10, "Building a MAPI-Enabled Forum
Tool"</a> </li>
<li><a HREF="#Chapter11CreatingaMAPIEMailAgen">Chapter 11, "Creating a MAPI E-Mail
Agent"</a> </li>
<li><a HREF="#Chapter12CreatingMicrosoftExchange">Chapter 12, "Creating Microsoft
Exchange Client Extensions"</a> </li>
</ul>
<hr>
<p>In this section of the book you learned the details of the Messaging API (MAPI)
services interface and how to use the various programming tools to access MAPI services.
Throughout the section you used the programming techniques and tools to build several
useful desktop applications including:
<ul>
<li><font COLOR="#000000">A simple e-mail client</font> </li>
<li><font COLOR="#000000">A mailing list server</font> </li>
<li><font COLOR="#000000">A forum tool</font> </li>
<li><font COLOR="#000000">A custom form for the Microsoft Exchange client</font> </li>
<li><font COLOR="#000000">An e-mail inbox agent</font> </li>
</ul>
<p>You learned that there are two versions of MAPI currently active-Simple MAPI (or MAPI
0) and MAPI 1.0. Simple MAPI is available through the MAPI controls that ship with Visual
Basic and through a library of Simple MAPI API calls. Most of the MAPI 1.0 features are
available via the OLE Messaging Library that is shipped with the MSDN Professional Level
CDs. The only MAPI services you cannot perform with the OLE Messaging Library are adding
new entries to the address book, and creating and deleting folders from the message store.
For this you need the power of C++ and access to the full MAPI 1.0 API set. </p>
<p>Here's a short summary of each of the chapters in Part II: </p>
<h2><a NAME="Chapter3WhatIsMAPI"></a><b><a HREF="ch3.htm">Chapter 3</a><font SIZE="5"
COLOR="#FF0000">, "What Is MAPI?"</font></b></h2>
<p>This chapter explained that the Messaging Application Programming Interface (MAPI) is a
part of the Windows Open Systems Architecture (WOSA) model. MAPI is designed to offer
three key benefits over other messaging services:
<ul>
<li><i>Flexibility</i>-Since MAPI is implemented within the WOSA model, there are three
distinct layers: </li>
<li><font COLOR="#000000">The client layer (the end-user software)</font> </li>
<li><font COLOR="#000000">The MAPI DLL layer (the MAPI service broker)</font> </li>
<li><font COLOR="#000000">The service layer (the actual message service provider)</font> </li>
<li>Because the MAPI DLL layer acts as the service request broker between the MAPI client
and the MAPI server, you can interchange servers and clients without having to modify your
MAPI software modules. </li>
<li><i>Consistency</i>-MAPI services and the methods for accessing them are the same no
matter what vendor you use to provide the message services. </li>
<li><i>Portability</i>-MAPI services are available on all supported versions of Windows
(Win3.11, WFW, WinNT, and Win95). As Microsoft moves WOSA services to <br>
non-Windows platforms, MAPI services will be available within those operating systems,
too. </li>
</ul>
<p>There are three general types of MAPI messages:
<ul>
<li><i>Text messages</i>-These are the standard plain ASCII text messages commonly known as
e-mail. Some MAPI service providers support the use of rich-text formatted messages (for
example, the Microsoft Exchange Mail client). </li>
<li><i>Formatted documents and binary files</i>-These are word processing documents,
graphics files, databases, and so on. MAPI allows you to send these binary files as
attachments to the body of text messages. </li>
<li><i>Control messages</i>-These messages are used by operating systems and specialized
batch programs to relay information about the operating system, or to send commands that
tell remote machines how to process attached data or run special jobs. </li>
</ul>
<p>Finally, you learned about the various types of MAPI applications:
<ul>
<li><i>Electronic mail clients</i>-The sole purpose of these programs is to give users
direct access to the available MAPI services (for example, the Microsoft Mail Exchange
client that ships with Windows 95). </li>
<li><i>Message-aware applications</i>-These are programs that offer MAPI services as an
added feature. Usually these programs offer users a send button or menu option. The
standard output of the program can then be routed to another location through MAPI. The <tt><font
FACE="Courier">Send...</font></tt> menu option of Microsoft Word95 is an example of a
message-aware application. </li>
<li><i>Message-enabled applications</i>-These programs offer MAPI services as a basic part
of their functionality. Message-enabled applications usually will not operate properly
unless MAPI services are available to the workstation. Examples of message-enabled
applications are data entry forms that collect data and automatically route it to the
appropriate e-mail address, sometimes without asking the user for MAPI logons or
addresses. </li>
</ul>
<p>Two more application types are:
<ul>
<li><i>Electronic forms applications</i>-These programs are fully functional data entry
forms that are MAPI-enabled. Users can treat the form like any Windows program. Once data
entry is completed and the message is sent, the addressee can open the message and see the
same data form. </li>
<li><i>Message-driven applications</i>-These are programs that can inspect portions of a
message (body, header, attachments) and perform requested actions based on the contents of
the message parts. Examples of message-driven applications include e-mail filtering
agents, file transfer and update routines, and long-distance data search and retrieval
programs. </li>
</ul>
<h2><a NAME="Chapter4MAPIArchitecture"></a><b><a HREF="ch4.htm">Chapter 4</a><font
SIZE="5" COLOR="#FF0000">, "MAPI Architecture"</font></b></h2>
<p>In this chapter you learned about the general architecture of the MAPI system. You
learned that there are two main components to the system:
<ul>
<li><font COLOR="#000000">The MAPI Client</font> </li>
<li><font COLOR="#000000">The MAPI Server</font> </li>
</ul>
<p>The MAPI Client resides on the user's desktop and handles three main MAPI objects:
<ul>
<li><font COLOR="#000000">Messages and attachments</font> </li>
<li><font COLOR="#000000">Storage folders</font> </li>
<li><font COLOR="#000000">MAPI addresses</font> </li>
</ul>
<p><a HREF="ch4.htm">Chapter 4</a> also reviewed the basic properties and features of MAPI
messages, including message headers, folders, and address objects. </p>
<p>You learned that the MAPI Server usually resides on a stand-alone workstation connected
to the network (although not always). Like the MAPI Client, the MAPI Server handles three
main objects:
<ul>
<li><font COLOR="#000000">Message transports</font> </li>
<li><font COLOR="#000000">Message stores</font> </li>
<li><font COLOR="#000000">Address books</font> </li>
</ul>
<p>The MAPI model allows users to use multiple versions of message transports (such as
Microsoft Exchange Server messages and SMTP Internet messages), message storage, and
address books. You also learned about the MAPI Spooler, which moves items from the message
store to the appropriate provider. </p>
<h2><a NAME="Chapter5UsingtheMicrosoftExchange"></a><b><a HREF="ch5.htm">Chapter 5</a><font
SIZE="5" COLOR="#FF0000">, "Using the Microsoft Exchange Forms Designer"</font></b>
</h2>
<p>In this chapter you learned how to use the Microsoft Exchange Forms Designer kit that
ships with Microsoft Exchange Server. You learned how to design, code, test, and install
custom message forms for use at individual workstations or over a large network. </p>
<p>Topics in this chapter included:
<ul>
<li><font COLOR="#000000">Using the Microsoft Exchange Forms Designer</font> </li>
<li><font COLOR="#000000">Creating custom forms</font> </li>
<li><font COLOR="#000000">Testing and compiling custom forms</font> </li>
<li><font COLOR="#000000">Installing custom forms</font> </li>
</ul>
<p>You also learned how to set up Microsoft Exchange folders for use with custom forms.
Related topics included:
<ul>
<li><font COLOR="#000000">Creating shared folders</font> </li>
<li><font COLOR="#000000">Setting folder views, including sorting, filtering, and grouping
messages</font> </li>
<li><font COLOR="#000000">Installing custom forms in folders</font> </li>
</ul>
<h2><a NAME="Chapter6CreatingMAPIAwareApplicat"></a><b><a HREF="ch6.htm">Chapter 6</a><font
SIZE="5" COLOR="#FF0000">, "Creating MAPI-Aware Applications"</font></b></h2>
<p>In <a HREF="ch6.htm">Chapter 6</a> you learned how to use low-level MAPI function calls
to add e-mail capabilities to existing Windows applications. </p>
<p>You learned that MAPI-aware applications are programs that provide electronic send
and/or receive services as a part of their basic feature set. Mail-aware software is able
to use the available mail services in much the same way that programs use available
printers, modems, or storage media (disk drives, CD-ROMs, and so on). For example, most
office suite applications (word processors, spreadsheets, for example) provide a send
feature on the main menu of all their programs. Basically, whatever documents you can
create with the program can be sent to other locations using the mail services available
on the network. </p>
<p>You learned to add MAPI-aware features to an Excel spreadsheet by adding a few API
calls and some code to package up sections of the spreadsheet to be forwarded to another
e-mail user. </p>
<p>You also modified a text editor project built with Visual Basic 4.0 by adding a <tt><font
FACE="Courier">Send...</font></tt> option to the main menu. In this way you added MAPI
features to the application with a minimum of additional coding. </p>
<p>Part of this chapter described the details of the MAPI 0 API call set. This API set
gives you the same abilities as the Visual Basic 4.0 MAPI controls with a few advantages:
<ul>
<li><i>Crash protection</i>-Using the Visual Basic 4.0 MAPI controls will cause your program
to crash if MAPI services are not available at the workstation. Using the API set means
you can trap for missing MAPI services and modify your program accordingly. </li>
<li><i>Portability</i>-You can use the API call set with any VBA-compliant system, including
Access, Excel, and Word. You cannot use the Visual Basic MAPI controls with these
applications. </li>
</ul>
<h2><a NAME="Chapter7CreatingaSimpleMAPI"></a><b><a HREF="ch7.htm">Chapter 7</a><font
SIZE="5" COLOR="#FF0000">, "Creating a Simple MAPI Client with the MAPI
Controls"</font></b> </h2>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -