3.1.5.3 Sync Command Request

  • Article

A client uses the Sync command request ([MS-ASCMD] section 2.2.1.21) to synchronize its Calendar class items for a specified user with the calendar items that are currently stored by the server.

Any of the elements that belong to the Calendar class, as specified in section 2.2.2, can be included in a Sync command request.

Top-level Calendar class elements, as specified in section 2.2.2, can be transmitted as child elements of the airsync:ApplicationData element ([MS-ASCMD] section 2.2.3.11) within either an airsync:Add element ([MS-ASCMD] section 2.2.3.7.2) or an airsync:Change element ([MS-ASCMD] section 2.2.3.24).

In protocol versions 2.5, 12.0, 12.1, 14.0, and 14.1, top-level Calendar class elements can be transmitted as child elements of the airsync:Supported element ([MS-ASCMD] section 2.2.3.179) in order to support ghosted elements. A specific subset of the Calendar class elements is required in this instance. The full list is specified in [MS-ASCMD] section 2.2.3.179. In protocol version 16.0 and 16.1, all top-level Calendar class elements are ghosted when they are not present.

For more details about the Sync command, see [MS-ASCMD] section 2.2.1.21.