Share via

3.1.5.2 Out-of-Date Meetings

  • Article

A Meeting Request object or Meeting Update object becomes out-of-date when a more recent version is received and processed. A Meeting Response object is out-of-date when the attendee responds to an older Meeting Request object or Meeting Update object, instead of the most current Meeting Update object.

This section specifies how the client can determine whether the Meeting Request object or Meeting Response object is out-of-date. If one of the following conditions is true, the Meeting Request object or Meeting Response object is considered to be out-of-date:

  • The value of the PidLidMeetingType property (section 2.2.6.5) on the Meeting Request object is set to mtgOutofDate.

  • The sequence number of the Meeting object is greater than that of the Meeting Request object or Meeting Response object.

  • The sequence number of the Meeting object is the same as that of the Meeting Request object or Meeting Response object, but the value of the PidLidOwnerCriticalChange property (section 2.2.1.34) on the Meeting Request object or Meeting Response object is earlier than the request time of the Meeting object, where the request time is determined as shown in the following table.

    Recipient

    Property that specifies request time

    Organizer

    PidLidAppointmentSequenceTime (section 2.2.4.1)*

    Attendees

    PidLidOwnerCriticalChange

*If PidLidAppointmentSequenceTime (section 2.2.4.1) does not exist on the Organizer's item, the request time is the value of the associated object's PidLidOwnerCriticalChange property.

The value of the PidLidAttendeeCriticalChange property (section 2.2.5.2) on the Meeting Response object is less than the value of the PidTagRecipientTrackStatusTime property (section 2.2.4.10.3) on the RecipientRow structure ([MS-OXCDATA] section 2.8.3) of the organizer's Meeting object that represents the attendee.