2.2.3.11 CPMGetQueryStatusOut
The CPMGetQueryStatusOut message replies to a CPMGetQueryStatusIn message with the status of the query. The format of the CPMGetQueryStatusOut message that follows the header is shown in the following diagram.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
_Status |
|||||||||||||||||||||||||||||||
_Status (4 bytes): A 32-bit unsigned integer. A bitmask of values defined in the following tables that describe the query.
-
The following table lists STAT_* values obtained by performing a bitwise AND operation on _Status with 0x00000007. The result MUST be one of the following.
-
Constant
Meaning
STAT_BUSY
0x00000000
The asynchronous query is still running.
STAT_ERROR
0x00000001
The query is in an error state.
STAT_DONE
0x00000002
The query is complete.
STAT_REFRESH
0x00000003
The query is complete, but updates are resulting in additional query computation.
-
The following table lists additional STAT_* bits that can be set independently.
-
Constant
Meaning
STAT_NOISE_WORDS
0x00000010
Noise words were replaced by wildcard characters in the content query.
STAT_CONTENT_OUT_OF_DATE
0x00000020
The results of the query might be incorrect because the query involved modified but unindexed files.
STAT_REFRESH_INCOMPLETE
0x00000040
The results of the query might be incorrect because the query involved modified and indexed files whose content was not included.
STAT_CONTENT_QUERY_INCOMPLETE
0x00000080
The content query was too complex to complete or required enumeration instead of use of the content index.
STAT_TIME_LIMIT_EXCEEDED
0x00000100
The results of the query might be incorrect because the query execution reached the maximum allowable time.