WebDAV Notifications evaluation criteria

Exchange

Find evaluation criteria information for Exchange WebDAV Notifications.

Last modified: November 05, 2013

Applies to: Exchange Server 2003 | Exchange Server 2007

In this article
Functional criteria for WebDAV Notifications
Development criteria for WebDAV Notifications
Security criteria for WebDAV Notifications
Deployment criteria for WebDAV Notifications
Additional resources

Exchange WebDAV Notifications are used to perform event-based processing in a web-based document storage environment. WebDAV Notifications allow a client application to perform actions based on changes in the state of data stored on the server, including creating, updating, and moving documents, and processing new email messages. Exchange WebDAV Notifications help client applications display up-to-date information or inform the end user of document updates by another user.

WebDAV Notifications sent from the server to the subscribing client use UDP packets (HTPU), sent on the port specified in the subscription. Depending on your network configuration, notifications generated for subscriptions with HTTP URLs across the Internet might be blocked by the Internet firewall.

Note Note

WebDAV is deemphasized in Exchange Server 2007 and is not available in versions of Exchange starting with Exchange Server 2010.

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

Table 1:  WebDAV Notifications functional criteria

Criterion

Description

Application function

WebDAV Notifications are typically used in remote client applications that already use WebDAV to communicate with the Exchange server. This might include web-based messaging clients and collaboration applications that use Exchange public folders.

Availability

WebDAV Notifications are available in Exchange 2003 and Exchange 2007. Versions of Exchange starting with Exchange 2010 do not include WebDAV.

Application architectures

Typically, web-based, thin-client applications use WebDAV. However, you can create traditional Windows GUI applications that use WebDAV to communicate with the Exchange server. WebDAV is also often used for communication between an application middle tier and the Exchange server.

Remote usage

WebDAV is often ideal for remotely accessing Exchange. Because it uses the same ports that HTTP and HTTPS use to communicate, you do not have to configure corporate firewalls and routers.

Major objects

WebDAV Notifications do not present any objects.

Data access model

WebDAV returns information in text and XML streams that contain the item data, properties, and error information. Additional information is available in the method response headers.

Threading models

Application threading is dependent on the client application threading model and does not affect WebDAV. Because WebDAV is an extension of HTTP, no connection state information is retained between transactions. However, items status is retained on the Exchange server, for example in response to a WebDAV resource lock command.

Transactions

WebDAV Notifications do not support transactions.

Management capabilities

You can use the Exchange administration console, CDOEXM, and WMI to managed WebDAV virtual servers manually and programmatically. WebDAV Notifications are a feature of WebDAV.

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

Table 2:  WebDAV Notifications development criteria

Criterion

Description

Languages and tools

Because WebDAV is a protocol, you can use any programming tool and language that sends and receives HTTP requests and responses, such as the MSXML HTTPRequest object, to create applications that use WebDAV to access Exchange.

Managed implementation

WebDAV is not a managed IIS extension. However, client applications that use WebDAV can use managed code as appropriate. Managed applications typically use the System.Net.HttpWebRequest object from the .NET Framework.

Scriptable

WebDAV is scriptable by means of the MSXML HTTPRequest object.

Test/debug tools

You do not need any special debugging tools to debug applications that use WebDAV. A network monitoring tool might be helpful for particularly difficult protocol interaction issues.

Expert availability

Developers who have created networked applications or who have experience using networking protocols are common.

Available information

Information about WebDAV Notifications is available in the Exchange Server 2003 SDK.

Developer/deployment licensing

Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the Exchange servers that store the data that your WebDAV applications access.

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

Table 3:  WebDAV Notifications security criteria

Criterion

Description

Design-time permissions

You do not need any specific permissions to use WebDAV Notifications with an Exchange server. The Exchange server must be configured to allow WebDAV access, and you must have permissions to access the data the application will use.

Setup permissions

Because applications that use WebDAV run on either the client or middle tier, typically no specific Exchange server permissions are needed for setup. If the Setup program makes changes in the Exchange store, for example to create the notification, the user running Setup must have permission to make those changes.

Run-time permissions

The authentication/authorization methods used between the client and the WebDAV virtual server determine the run-time permissions that WebDAV applications need. When the application tier that uses WebDAV to access the Exchange server includes a small number of computers, you might configure the virtual server to allow connections from only those middle-tier computers.

Built-in security features

By default, WebDAV virtual servers use Basic or NTLM authentication, and anonymous access is disabled. Because WebDAV transmits data in plaintext across the network, we also recommend that Exchange WebDAV virtual servers that transmit sensitive data use SSL/TLS.

Security monitoring features

WebDAV virtual servers use the IIS security monitoring features.

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

Table 4: WebDAV Notifications deployment criteria

Criterion

Description

Server platform requirements

The Exchange server that manages the store on which your application data is located must have a WebDAV virtual server if the client application accesses it directly. Alternatively, you can use WebDAV configured on Exchange front-end servers to receive notifications from all the stores in the domain for which the user has permissions.

Client platform requirements

WebDAV Notifications use UDP packets to notify the client that the Exchange store detected a subscribed event. The subscription command specifies the UDP port on which Exchange will contact the client computer. The client application must have a UDP listener running on the port specified on the subscription so that the events will be received. Note that because firewall configurations block UDP packets, WebDAV Notifications typically only work within an intranet or over a PPTP tunnel.

Deployment methods

Client applications that use WebDAV Notifications are deployed based on their client architecture and technology. The client or middle tier communicates via WebDAV with an Exchange server. WebDAV Notifications use UDP packets to contact the client application and therefore might be unsuitable for use across the Internet.

Deployment notes

None.

Show:
© 2014 Microsoft