Exchange Server Protocols Evaluation Criteria
This topic provides information about how to use the Microsoft Exchange Server protocols to develop applications that work with Exchange. The Exchange Server protocols include many different client-server interactions.
The Exchange Server protocols are intended for developers who create software and systems that interoperate with Exchange; for example, developers who work on network transport systems, or who need to verify the network traffic between their system and Exchange. The Exchange Server protocol documents are not structured like traditional API documentation; they use Request For Comments (RFC)–style specifications.
| Criteria | Description |
|---|---|
|
Application Domain |
The Exchange Server protocols are intended to be used by implementers of a wide variety of application types, network appliances, and other systems that must interact at a network level with or as a replacement for Exchange. |
|
Major Objects |
The Exchange Server protocols do not expose objects in the same way that a traditional API does. Some protocols are based on RPC, SMTP, HTTP, Web services, and other TCP/IP-based protocols. |
|
Data Access Model |
Not applicable. |
|
Threading Models |
The Exchange Server protocols do not require any particular threading model. The use of threaded application execution is an implementation-specific choice. |
|
Application Architectures |
The Exchange Server protocols do not require any particular application architecture. |
|
Remote Usage |
The Exchange Server protocols are all intended for interaction between a client and server over a network, and are each intended for computer-to-computer interaction. |
|
Transactions |
Some Exchange Server protocols support transactions, while others do not. |
|
Management Capabilities |
Any client- or server-management capabilities in the Exchange Server protocols are described in the respective protocol specifications. |
|
Availability |
The Exchange Server protocol specifications apply to Exchange 2010, Exchange 2007, and, in most cases, Exchange 2003. |
| Criteria | Description |
|---|---|
|
Languages and Tools |
The Exchange Server protocols are not tied to any particular programming language or tools, as they operate at the network level. |
|
Managed Implementation |
The Exchange Server protocols are not traditional APIs, in that they represent network traffic, and therefore do not appear in any Microsoft .NET namespaces. |
|
Scriptable |
Not Applicable |
|
Test/Debug Tools |
The Exchange Server protocols are generally debugged by using network monitoring software and equipment. |
|
Expert Availability |
Implementing complex network protocols is a moderately specialized skill. |
|
Available Information |
You can find information about the protocols at the Exchange Server Protocols site on MSDN. |
|
Developer/Deployment Licensing |
You can find information about licensing Microsoft protocols at the Microsoft Protocol Programs Web site. |
| Criteria | Description |
|---|---|
|
Design-Time Permissions |
No special developer permissions are required to use the Exchange Server protocols. Information that exists on a server that the protocol is trying to access is controlled through the authorization and authentication schemes specified in the protocol document. |
|
Setup Permissions |
Exchange Server protocols do not specify or restrict implemented application setup. |
|
Run-time Permissions |
No special run-time permissions are required to use the Exchange Server protocols. Information that exists on a server that the protocol is trying to access is controlled through regular authorization and authentication schemes, as specified in the protocol document. |
|
Built-in Security Features |
The built-in security features of each protocol are specified in the respective protocol document. |
|
Security Monitoring Features |
Security monitoring of an implemented protocol is the responsibility of the implementer. Exchange Server and Windows may provide security monitoring that can assist in debugging issues; however, they cannot replace effective security monitoring features of the implemented system. |
| Criteria | Description |
|---|---|
|
Server Platform Requirements |
Exchange Server protocols do not put requirements on the server platform that an implemented solution is run non. Exchange Server must be run on a compatible operating system. |
|
Client Platform Requirements |
Exchange Server protocols do not put requirements on the client platform that an implemented solution is run on. |
|
Deployment Methods |
Exchange Server protocols do not put requirements on the methods by which an implemented solution is deployed. |
|
Deployment Notes |
None. |
