Share via

6 Appendix A: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft FAST Search Server 2010

  • Microsoft SharePoint Foundation 2010

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 1.4:  Applications SHOULD interact with an OLE DB interface wrapper such as a protocol client, and not directly with the protocol. For more information, see [MSDN-OLEDBP-OI].

<2> Section 1.8:  Search uses only the values specified in [MS-ERREF].

<3> Section 1.8:  See [MSDN-PROPSET] for a list of supported property sets.

<4> Section 2.2.1.19:  In SharePoint Foundation 2010 implementation, alternative spellings are not generated and the SpellingSuggestion field always contains an empty string.

<5> Section 2.2.2:  In Microsoft Search Server 2010, Microsoft Search Server 2010 Express, SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 implementations, the protocol client always sets the _status field to 0x00000000.

<6> Section 2.2.3.1:  In Search Server 2010, Search Server 2010 Express, SharePoint Foundation 2010 and SharePoint Server 2010 implementations, the _iClientVersion is always set to 0x00010102.

<7> Section 2.2.4:  The same pipe connection is used for the following messages, except when the error is returned in a CPMConnectOut message. In the latter case, the pipe connection is terminated by the client by closing the named pipe handle. Whenever the client end of the pipe is closed, the server releases all resources associated with the connection, including the named pipe instance.

<8> Section 3.2.4.1.5:  For a 32-bit protocol client talking to a 32-bit protocol server or a 64-bit protocol client talking to a 64-bit protocol server, this value is set to a memory address of the receiving buffer in the application process. This allows for pointers received in the Rows field of CPMGetRowsOut to be correct memory pointers in a client application process. Otherwise, it is set to "0x00000000".