2.5.10.5 Protocol-Specific Details

Using remote operations (ROPs)

Finding folder items by using ROPs

Figure 26: Finding folder items by using ROPs

Note The ROPs are sent via RPC or MAPI extensions for HTTP. Several ROPs can be batched into a single request, as described in [MS-OXCROPS].

  1. The client opens the specified folder per the use case described in section 2.5.9.

  2. The client issues a RopGetContentsTable ROP request ([MS-OXCROPS] section 2.2.4.14) with a handle to the folder for which to open the contents table.

  3. The Exchange server responds with a handle to the contents table.

  4. The client builds the search criteria by constructing a restriction, as described in [MS-OXCDATA].

  5. The client issues a RopRestrict ROP request ([MS-OXCROPS] section 2.2.5.3) with the constructed restriction to establish the search criteria.

  6. The Exchange server responds to the RopRestrict ROP request.

  7. The client can optionally issue a RopSortTable ROP request ([MS-OXCROPS] section 2.2.5.2) to specify a series of sort columns in the resulting table.

  8. The Exchange server responds to the RopSortTable ROP request.

  9. The client prepares a list of desired properties to retrieve and issues a RopSetColumns ROP request ([MS-OXCROPS] section 2.2.5.1) to indicate the desired property columns.

  10. The Exchange server responds to the RopSetColumns ROP request.

  11. The client issues a RopQueryRows ROP request ([MS-OXCROPS] section 2.2.5.4) with a contents table handle (HCT) to retrieve rows from the contents table.

  12. The Exchange server responds with a table of rows, where each row represents a message in the folder that matches the search criteria from step 4, and each column corresponds to the properties indicated in step 8.

Using WebDAV

Finding folder items by using WebDAV

Figure 27: Finding folder items by using WebDAV

  1. The client issues a SEARCH method request, as described in [MS-WDVSE], to the Exchange server as the Request-URI, referencing the desired folder path to perform the search. The search criteria are expressed in the XML body of the request.

  2. The Exchange server responds with HTTP status code 207 (Multi-Status) and a series of responses, where each response corresponds to a matching entry in the folder.

Using Exchange ActiveSync

Finding folder items by using Exchange ActiveSync

Figure 28: Finding folder items by using Exchange ActiveSync

  1. The client issues a Search command request, as described in [MS-ASCMD] section 2.2.2.16, by specifying the name of the folder to be searched, and an XML query that represents the search criteria.

  2. The Exchange server responds with HTTP status code 200 (OK) and a collection of results, where each result corresponds to an item in the folder that matches the search criteria.

Using Exchange Web Services

Finding folder items by using Exchange Web Services

Figure 29: Finding folder items by using Exchange Web Services

  1. The client uses the HTTPS/SOAP FindItemSoapIn request message, as described in [MS-OXWSSRCH] section 3.1.4.2.1.1, to find specific items from one or more folders. The client can specify the list of folders to search, the list of properties to return, the search criteria, and the sort order of the results, among other options.

  2. The Client Access server responds with a FindItemSoapOut response message, as described in [MS-OXWSSRCH] section 3.1.4.2.1.2, which includes the ResponseCode element specifying the status of the operation and the set of items that match the search criteria.

Show: