Export (0) Print
Expand All

1.7 Versioning and Capability Negotiation

This document covers versioning issues in the following areas:

  • Localization: Localization-related aspects of the protocol are described in section 2.2.3.1.1.1.2.

  • Capability Negotiation: This protocol performs explicit capability negotiation by using the following ROPs, properties, and flags. Support of the following features is determined by the versions of the client and server that are supplied either by the EcDoConnectEx method, as described in [MS-OXCRPC], or by the X-ClientApplication and X-ServerApplication headers of the Connect request type request and response, as described in [MS-OXCMAPIHTTP]. Both the client and server limit their behavior to the capabilities supported by the other. For more information, see [MS-OXCRPC] section 3.1.4.1.3.

Client version

Description

11.0.0.4920 and above

The client supports receiving the 0x00000480 value in the ReturnValue field of the RopFastTransferSourceGetBuffer ROP (section 2.2.3.1.1.5) response.

12.0.3730.0 and above

The client supports send optimization for ICS using the PidTagTargetEntryId property ([MS-OXOMSG] section 2.2.1.76). For more information, see section 3.3.4.3.3.2.1.2.

Server version

Description

8.0.359.0 and above

The server supports the PartialItem flag of the SendOptions field, as described in section 2.2.3.2.1.1.1. Earlier server versions do not support this flag.

The RopTellVersion ROP is used to explicitly declare capabilities of the servers in the server-to-client-to-server upload scenario. For more information, see section 3.3.4.2.1.

Show:
© 2014 Microsoft