Collaboration Data Objects for Windows 2000 (CDOSYS) evaluation criteria

Exchange

Published: July 16, 2012

Find evaluation criteria information for Collaboration Data Objects for Windows 2000 (CDOSYS).

Applies to:  Exchange Server 2003 | Exchange Server 2007 

In this article
Functional criteria for CDOSYS
Development criteria for CDOSYS
Security criteria for CDOSYS
Deployment criteria for CDOSYS
Additional resources

CDOSYS (Cdosys.dll), which implements the 2.0 version of the Collaboration Data Objects API specification, is a Component Object Model (COM) component that simplifies the development of programs that create or manipulate Internet messages. CDOSYS is one in a suite of collaborative COM components referred to collectively as CDO.

The following table lists and describes the functional criteria for CDOSYS. For descriptions of the functional criteria, see Functional criteria in the Exchange development technology evaluation criteria descriptions article.

Table 1:  CDOSYS functional criteria

Criterion

Description

Application function

CDOSYS is used in applications that create and send messages by means of Simple Mail Transfer Protocol (SMTP) and the Network News Transfer Protocol (NNTP), and by ASP applications with messaging capabilities. CDOSYS also includes transport event sinks. For more information about the transport event sinks, see Collaboration Data Objects for Windows (CDOSYS) SMTP/NNTP event sinks evaluation criteria.

Availability

CDOSYS in included in the Windows XP and Windows Server 2003 operating systems.

Application architectures

CDOSYS is commonly used for client-side Windows applications that use simple email and NNTP messaging and for ASP-based applications that require simple messaging capabilities.

Remote usage

CDOSYS is installed with Windows and sends email messages by using standard network protocols. Applications that run on an Exchange server typically use CDO for Exchange 2000 Server (CDOEX).

Major objects

CDOSYS provides the following COM/Automation-compatible classes that represent messages and their parts: Messages, Message, BodyPart, BodyParts, Configuration, and DropDirectory. CDOSYS also defines the COM interfaces that SMTP and NNTP protocol events must implement to function properly.

Data access model

Collections of messages and body parts in CDOSYS applications are presented as ADO row sets, while individual messages are represented as a collection of body part objects.

Threading models

Applications that use CDOSYS do not have any specific threading restrictions. However, applications that use free-threading should not share CDOSYS object instances among asynchronously operating threads.

Transactions

Transactions are not supported with CDOSYS.

Management capabilities

CDOSYS does not generate Windows Event Log entries, and no performance counters are available to measure it.

The following table lists and describes the development criteria for CDOSYS. For descriptions of the development criteria, see Development criteria in the Exchange development technology evaluation criteria descriptions article.

Table 2:  CDOSYS development criteria

Criterion

Description

Languages and tools

CDOSYS can be used with any COM/Automation-compatible languages, as well as with non-COM languages such as C/C++.

Managed implementation

CDOSYS is an unmanaged component. The use of CDOSYS is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework, but we recommend that you use System.Web.Mail namespace to send email messages in a managed code environment.

Scriptable

CDOSYS is scriptable by means of ASP and the Windows Scripting Host (WSH).

Test/debug tools

You do not need any special debugging tools to debug applications that use CDOSYS.

Expert availability

You can find developers who have experience with CDOSYS in Microsoft and third-party websites and communities.

Available information

CDOSYS is covered in several Microsoft and third-party books. For more information about CDOSYS, see About CDO for Windows 2000 on MSDN.

Developer/deployment licensing

You do not need any special licenses to use CDOSYS. Depending on your configuration, your systems might require access to an additional SMTP/NNTP server to transport messages to their destination.

The following table lists and describes the security criteria for CDOSYS. For descriptions of the security criteria, see Security criteria in the Exchange development technology evaluation criteria descriptions article.

Table 3:  CDOSYS security criteria

Criterion

Description

Design-time permissions

You do not need any special permissions to use CDOSYS. However, you might need permissions to debug applications as part of troubleshooting. When you create applications that send email messages, you need either write access to the pickup directory or read access to the IIS metabase, so that the application can determine the SMTP port to use to send email messages.

Setup permissions

Users do not need any special permissions to install applications that use CDOSYS beyond those that they need to install applications of a similar architecture. If the Setup program makes configuration changes to a local SMTP or NNTP service, the user must have sufficient permissions to make those changes.

Run-time permissions

No special permissions are required to run interactive applications or ASP pages to enable the use of CDOSYS. In applications that use the SMTP or NNTP drop directory, the application or user must have permission to write to that directory. When running an application that sends email messages, the user will need either write access to the pickup directory or read access to the IIS metabase, so that the application can determine the SMTP port to use to send mail.

Built-in security features

CDOSYS uses the underlying Windows Server 2003 security features.

Security monitoring features

None.

The following table lists and describes the deployment criteria for CDOSYS. For descriptions of the deployment criteria, see Deployment criteria in the Exchange development technology evaluation criteria descriptions article.

Table 4:  CDOSYS deployment criteria

Criterion

Description

Server platform requirements

CDOSYS is available on Windows XP and Windows Server 2003. CDOSYS requires access to an SMTP or NNTP server to transfer the messages it creates. If this is a local IIS service, the application must be able to determine the local pickup directory or the SMTP port of the local service.

Client platform requirements

CDOSYS applications run on Windows XP.

Deployment methods

You can use standard software distribution technologies to deploy applications that use CDOSYS.

Deployment notes

On systems where Exchange 2003 is installed, the CDOSYS components are replaced by CDO for Exchange 2000 Server (CDOEX). For more information about CDOEX, see Collaboration Data Objects for Exchange (CDOEX) evaluation criteria.

The computer on which you install a CDOSYS application must be running an operating system that includes CDOSYS.

Community Additions

ADD
Show:
© 2014 Microsoft