Rediger

Del via


Protocol Handlers Interfaces

This Windows Search reference section consists of protocol handler interfaces.

In this section

Topic Description
IItemPropertyBag
Defines methods to obtain information about the properties of a search item. This interface is supported only on Windows XP and Windows Server 2003, and should no longer be used.
IOpLockStatus
Provides methods to check the opportunistic lock that is used by Microsoft Windows Desktop Search (WDS) on items while indexing. If another process locks the file in an incompatible manner, WDS will lose its lock and allow the other process to have the file. This mechanism allows WDS to run in the background. Consequently, WDS needs to check its locks to ensure another process has not taken precedence while WDS indexes the item.
A third-party IUrlAccessor object can implement this interface if the underlying data store provides a mechanism to track concurrent access to items. If this interface is exposed by IUrlAccessor, WDS will check the IOpLockStatus while indexing items from that store.
IProtocolHandlerServices
IProtocolHandlerSite
Provides methods for a protocol handler's IUrlAccessor object to query the Filter Daemon for the appropriate filter for the URL item.
ISearchProtocol
Provides methods for invoking, initializing, and managing IUrlAccessor objects. Methods in this interface are called by the protocol host when processing URLs from the gatherer.
The protocol handler implements the protocol for accessing a content source in its native format. Use this interface to implement a custom protocol handler to expand the data sources that can be indexed.
ISearchProtocol2
Provides methods for invoking, initializing, and managing IUrlAccessor objects. Methods in this interface are called by the protocol host when processing URLs from the gatherer.
The protocol handler implements the protocol for accessing a content source in its native format. Use this interface to implement a custom protocol handler to expand the data sources that can be indexed.
ISearchProtocolThreadContext
This optional interface enables the protocol handler to perform an action on the thread used for filtering in the protocol host. When the protocol host starts, it first initializes all the protocol handlers, and then it creates the filtering thread(s). The methods on this interface enable protocol handlers to manage their resources that are used by a filtering thread.
ISearchProtocolUI
Provides a method for invoking ISearchItem objects. Methods in this interface are called by the protocol host when processing URLs from the gatherer. The protocol handler implements the protocol for accessing a content source in its native format, and this interface implements a custom protocol handler to expand the data sources that can be indexed.
IUrlAccessor
Provides methods for processing an individual item in a content source whose URL is provided by the gatherer to the filter host.
IUrlAccessor2
Extends functionality of the IUrlAccessor interface.
IUrlAccessor3
Extends the functionality of the IUrlAccessor2 interface with the IUrlAccessor3::GetImpersonationSidBlobs method to identify user security identifiers (SIDs) for a specified URL.
IUrlAccessor4
Extends the functionality of the IUrlAccessor3 interface with the IUrlAccessor4::ShouldIndexItemContent method that identifies whether the content of the item should be indexed.