Table of Contents
Advertisement
How the Server Associates Plug-Ins with OIDs
When the server encounters the OID for a matching rule, it attempts to find the
plug-in associated with that matching rule.
If no plug-in is associated with the matching rule, the server calls each matching
rule plug-in to find one that handles the specified matching rule.
When the server finds a plug-in that handles the matching rule, the server creates
an association between the plug-in and the matching rule OID for future reference.
If no matching rule plug-in supports the specified OID, the server returns an
LDAP_UNAVAILABLE_CRITICAL_EXTENSION
Finding a Plug-In for Indexing
To determine which matching rule plug-in is responsible for indexing an attribute
with a given matching rule (based on its OID), the server does the following for
each plug-in:
In a new
1.
Slapi_PBlock
SLAPI_PLUGIN_MR_OID
Next, the server calls the indexer factory function (specified in the
2.
SLAPI_PLUGIN_MR_INDEXER_CREATE_FN
The server checks the
3.
If the parameter is NULL, the plug-in does not handle the matching rule
specified by that OID.
If the parameter returns an indexer function, this plug-in handles the
matching rule specified by that OID.
Finally, the server frees the parameter block from memory.
4.
At some point in time, the server may also call the indexer destructor function
(specified in the
SLAPI_PLUGIN_MR_DESTROY_FN
object that was created by the indexer factory function.
error back to the client.
parameter block, the server sets the OID in the
parameter.
parameter) for the plug-in.
SLAPI_PLUGIN_MR_INDEX_FN
Chapter 11
Understanding Matching Rule Plug-Ins
parameter.
parameter) to free the indexer
Writing Matching Rule Plug-Ins
127
Advertisement
Table of Contents
