2.1.3.1 Best Body Algorithm

The Best Body Algorithm specifies the algorithm that the client uses to determine the best body format of a message.

Step 1. Issue a RopGetPropertiesSpecific ROP request ([MS-OXCROPS] section 2.2.8.3) for the following properties: PidTagBody ([MS-OXPROPS] section 2.618), PidTagRtfCompressed ([MS-OXPROPS] section 2.942), PidTagHtml ([MS-OXPROPS] section 2.734), and PidTagRtfInSync ([MS-OXPROPS] section 2.943). The client SHOULD also request PidTagNativeBody ([MS-OXPROPS] section 2.806).

If the RopGetPropertiesSpecific ROP returns a status code that indicates a failure, then the body type is undefined and the algorithm exits.

If the client does not request all three of the body type properties (PidTagBody, PidTagRtfCompressed, and PidTagHtml), the server SHOULD<2> return the best value for the PidTagNativeBody property that fits one of the requested body types.

If the client retrieves all five property values and the value of the PidTagNativeBody property is as specified in the following table, then the server has already saved the best body format to use in the value of the PidTagNativeBody property. In this case, it is not necessary to perform the remainder of the algorithm specified in this section.

If the server returns a value for the PidTagNativeBody property, the client SHOULD use this value to determine the best body. Otherwise, the client proceeds to step 2. The following table identifies the best body format that corresponds to the value. If the PidTagNativeBody property is missing or the value is not provided in the following table, proceed to the remaining steps of the algorithm.

If the server does not return the PidTagNativeBody property but does return the remaining four property values, then the RopGetPropertiesSpecific ROP returns a StandardPropertyRow structure ([MS-OXCDATA] section 2.8.1.1). If any of the four property values were not retrieved, then the RopGetPropertiesSpecific ROP returns a FlaggedPropertyRow structure ([MS-OXCDATA] section 2.8.1.2).

Step 2. Create four variables: PlainStatus, RtfStatus, HtmlStatus, and RtfInSync. Examine the returned property values and assign values to the corresponding variables as follows. In each case, if there is an error code, then the value for the variable is either NotFound or NotEnoughMemory.

• PlainStatus – If the RopGetPropertiesSpecific ROP returned a StandardPropertyRow structure, or the value of the PidTagBody property is a PtypString ([MS-OXCDATA] section 2.11.1), then assign the NoError error code to the PlainStatus variable; else copy the error code from the FlaggedPropertyValue structure to the PlainStatus variable.

• RtfStatus - If the RopGetPropertiesSpecific ROP returned a StandardPropertyRow structure, or the value of the PidTagRtfCompressed property is a PtypBinary ([MS-OXCDATA] section 2.11.1) value, then assign the NoError error code to the RtfStatus variable; else copy the error code from the FlaggedPropertyValue structure to the RtfStatus variable.

• HtmlStatus - If the RopGetPropertiesSpecific ROP returned a StandardPropertyRow structure, or the value of the PidTagHtml property is a PtypBinary value, then assign the NoError error code to the HtmlStatus variable; else copy the error code from the FlaggedPropertyValue structure to the HtmlStatus variable.

• RtfInSync - If the RopGetPropertiesSpecific ROP returned a StandardPropertyRow structure, or the value of the PidTagRtfInSync property is PtypBoolean ([MS-OXCDATA] section 2.11.1), then copy the PtypBoolean value to the RtfInSync variable; else assign FALSE to the RtfInSync variable.

Step 3. Determine the body format based on values of the four variables created in step 2. The following table can be implemented as an "if-then-else" chain, in exactly the order specified.

This table can be implemented by using the following pseudocode. Each row of the table is one clause of an "if-else-if" chain. Within a row, each column is ANDed together to form the condition of an "if" clause. If there is a case that is not defined, then the BodyFormat is plain text.