Writing A Filter Factory Function - Netscape DIRECTORY SERVER 6.2 - PLUG-IN Manual

If the query operator is
the index that match the value specified in the search filter. In the case of the other
query operators, the server attempts to find ranges of keys that match the value.

Writing a Filter Factory Function

The filter factory function takes a single
should be thread-safe. The server may call this function concurrently. (Each
incoming LDAP request is handled by a separate thread. Multiple threads may call
this function if processing multiple requests that have extensible match filters.)
The filter factory function should do the following:
Get the OID from the
1.
whether or not that OID is supported by your plug-in.
If the OID is not supported, you need to return the result code
LDAP_UNAVAILABLE_CRITICAL_EXTENSION
to the client.
If the OID is supported, continue with this process.
Get and check the values of the
2.
SLAPI_PLUGIN_MR_VALUE
The values of these parameters are the attribute type and value specified in the
extensible match filter.
You can also get any data that you set in the
3.
parameter during initialization. (See "Writing an Initialization Function" on
page 143.)
Create a filter object, putting the following information in the object:
4.
The official OID of the matching rule (optional)
The attribute type specified in the filter
The value specified in the filter
Any additional data that you want made available to the filter index
function (for example, the query operator, if specified in the filter)
The server will call your filter index function at a later time to extract this
information from the filter object.
, the server attempts to find the keys in
SLAPI_OP_EQUAL
Slapi_PBlock
SLAPI_PLUGIN_MR_OID
SLAPI_PLUGIN_MR_TYPE
parameters.
Chapter 11
Handling Extensible Match Filters
argument. This function
parameter and determine
. The server will send this back
and
SLAPI_PLUGIN_PRIVATE
Writing Matching Rule Plug-Ins 137