Notifying the Index of Changes
[Windows Search 2.x is obsolete after Windows XP. Instead, use Windows Search.]
With Microsoft Windows Desktop Search (WDS) 2.6, protocol handlers for a given data store can tell the WDS Indexer when data in their store has changed. This improves performance by ensuring the Indexer doesn't crawl the entire store on incremental indexes. Using notification APIs, protocol handlers can notify the Indexer that an item has been moved or deleted, and they can add scopes to the WDS Indexer's crawl queue of URLs requiring indexing. Notification is helpful for applications such as email, where the protocol handler monitors the store and notifies the Indexer that items have changed and require indexing.
Protocol handlers notify the Indexer of changes through the ISearchItemsChangedSink interface. Information about data changes should be collected in SEARCH_ITEM_CHANGE structs and SEARCH_KIND_OF_CHANGE enumeration types and then communicated to the Indexer through the OnItemsChanged method of the ISearchItemsChangedSink interface.
To access this interface, a custom protocol handlers must first instantiate an ISearchManager object to gain access to the ISearchCatalogManager object. From there, one can instantiate an ISearchItemsChangedSink object and notify the Indexer of the data changes.
The OnItemsChanged method lets you collect and communicate data changes to your customer data store to initiate indexing.
|In||dwNumberofChanges||Total number of changes in the notification.|
|In||DataChangeEntries||All change notifications in an array of SEARCH_ITEM_CHANGE structures.|
|Out||dwBatchId||The batch ID that will be passed back with errors.|
|Out||hrCompletionCodes||Indicates whether each URL was accepted for indexing.|
The SEARCH_ITEM_CHANGE structure identifies the kind of change that occurred as well as the item's current URL and previous URL, if applicable. The structure is defined as follows:
|Property Name||Property Type||Description|
|Change||SEARCH_KIND_OF_CHANGE||The type of change that is being notified.|
|URL||LPWSTR||The URL for the object that has changed.|
|OldURL||LPWSTR||If the notification is a move, the old URL is provided and must be unique.|
|Priority||SEARCH_NOTIFICATION_PRIORITY||The priority of the change.|
The SEARCH_KIND_OF_CHANGE enumeration is defined as follows:
|SEARCH_CHANGE_ADD||0||The notification is for an additional URL.|
|SEARCH_CHANGE_DELETE||1||The notification is for the deletion of a URL.|
|SEARCH_CHANGE_MODIFY||2||The notification is that a URL has been modified.|
|SEARCH_CHANGE_MOVE_RENAME||3||The notification is for the move and rename of an object to a new URL.|
|SEARCH_CHANGE_SEMANTICS_DIRECTORY||0x10000||The notification is for a container URL.|
|SEARCH_CHANGE_SEMANTICS_SHALLOW||0x20000||The notification is for a container URL that should only have its container properties indexed.|
|SEARCH_CHANGE_SEMANTICS_SECURITY||0x40000||The notification is for a URL or container URL that has had its security properties changed.|
The SEARCH_NOTIFICATION_PRIORITY enumeration is defined as follows:
|SEARCH_NORMAL_PRIORITY||0||Only a normal priority should be used when indexing the URL. These notifications are processed before the normal background incremental indexing of a user's files and stores.|