MAPI or CDO? Sample Performance Tests.

Home

Development

Partners

Resellers

About

The Messaging API is a COM-like API that provides access to the contents of messaging stores. "Extended MAPI in Delphi" is a package providing access to Outlook-compatible objects through a COM-based API...

MAPI - CDO Address Book Sample Performance Tests
This is a sample application, that demonstrates MAPI/CDO differences and performance.

Differences Between CDO, Simple MAPI, and Extended MAPI
(according Microsoft)

MAPI (Messaging Application Programming Interface)

A messaging architecture and a client interface component.
As a messaging architecture, MAPI enables multiple applications to interact with multiple messaging systems across a variety of hardware platforms.
As a client interface component, MAPI is the complete set of functions and object-oriented interfaces that forms the foundation for the MAPI subsystem's client application and service provider interfaces. In comparison with Simple MAPI, Common Messaging Calls (CMC), and the Active Messaging Library (CDO), MAPI provides the highest performance and greatest degree of control to messaging-based applications and service providers.

CDO Microsoft® Collaboration Data Objects

A technology for building messaging or collaboration applications. Also called OLE Messaging; in version 1.1 it was called Active Messaging. It is designed to simplify the creation of applications with messaging functionality, or to add messaging functionality to existing applications.
CDO is MAPI shell, or in other word, CDO does not represent a new messaging model, but rather an additional scripting interface to the Messaging Application Programming Interface (MAPI) model.

The following figure shows the CDO Library as a layer that is built on top of MAPI. This is similar to the way function calls to the Common Messaging Calls (CMC) interface are mapped to the underlying MAPI interfaces.

It is important to recognize that the CDO Library does not offer access to all of the features of MAPI. In particular, it is designed primarily for clients and is not suitable for service providers.

The following table summarizes the programming interfaces that Microsoft provides for MAPI.

Programming interface	Description
Simple MAPI	Functions for Visual Basic version 3.0 and later, Visual Basic for Applications, DELPHI, and C/C++ client developers that allow access to the Inbox (no access to MAPI properties). Most developers should probably use either CMC or MAPI rather than Simple MAPI.
CDO Library	Programmable messaging objects for Visual Basic/Visual Basic for Applications, DELPHI and C/C++ developers.
MAPI	OLE Component Object Model (COM) interfaces for DELPHI*, C/C++ developers. Full access to all MAPI programming interfaces. Implemented and called by clients, service providers, and MAPI itself.

DELPHI* - with custom kit.

MAPI - CDO Address Book Application, only enumerate (count) recipients on Global Address Book (Microsoft Exchange Server GAL). The following table summarizes result:

Users/Mailbox	Time (min:sec:msec)**
	MAPI	CDO
10	00:00:019	00:00:120
100	00:00:150	00:01:612
500	00:00:882	00:10:856
1000	00:01:973	00:25:847

**
Tested with:
CPU 1 - Genuine Intel x86 Family 5 Model 4 Stepping 3
~233 MHz (Pentium 233 MMX)
System BIOS - Award Modular BIOS v4.51P
Total Physical Memory - 163256 KB (160MB)
OS Type - Microsoft (R) Windows NT (TM) Server
Version - Version 4.0 (Build 1381: Service Pack 6)

CPU/OS Processes - 49
Microsoft Exchange Server Version 5.5
(Build 2650.24: Service Pack 3)
DELPHI Version 5.0 (Build 5.62)

Compiled Application: MAPICDOExe.zip

For more information, please write

Extended MAPI in DELPHI

The Extended MAPI is one of the first COM technologies provided by Microsoft. Extended MAPI is core API for Microsoft Exchange Server, Microsoft Outlook, CDO, messaging.
We provide lots of examples, which demonstrates how inside DELPHI you can get the Extended MAPI power in your hands.

CDO 1.2.1 in DELPHI

A few examples how using CDO we can improve our productivity for small messaging (MAPI) applications.
Examples are Microsoft Exchange Server 5.5/2000/2003 compatibles
DELPHI 5/6/7/2005/2006/Turbo Delphi compatibles

Down to the Metal

After a few years of investigating and building Extended MAPI clients applications, we shifted part of our development team to the "MAPI inferno" - the service providers. This area of MAPI cannot be done with any kind of third-party custom MAPI components we know - they all have proved inapplicable here. Each MAPI service provider is unique, and moreover - they work in opposite sides.

IMI Microsoft Office Access Based Address Book
for Outlook 95/2007

IMI Microsoft Office Access Based Message Store
for Outlook 95/2007