How the Server Uses Parameter Blocks
The server uses parameter blocks as a means to pass information to and from your
plug-in functions.
When calling your matching rule plug-in functions, the server will create a new
Slapi_PBlock
parameter block to your function. After retrieving output parameters from the
block, the server typically frees the parameter block from memory.
In general, you should not expect a parameter block to be passed from plug-in
function to plug-in function. For example, the value of a parameter set by one
plug-in function may not necessarily be accessible to other plug-in functions, since
each function is usually passed a new and different parameter block.
Indexing Based on Matching Rules
This section explains how to set up the server to index entries using a matching
rule. The following topics are covered:
•
How the Server Sets Up the Index
•
How the Server Updates the Index
•
Writing the Indexer Factory Function
•
Getting and Setting Parameters in Indexer Factory Functions
•
Writing the Indexer Function
•
Writing the Indexer Function
Note that you also need to define an initialization function to register your indexer
factory function.
How the Server Sets Up the Index
When the server encounters a matching rule OID in an
server configuration file, the server determines which plug-in supports the
matching rule identified by the OID. See "How the Server Associates Plug-Ins with
OIDs" on page 127 for details.
parameter block, set some input parameters, and pass the
Indexing Based on Matching Rules
directive in the
index
Chapter 11
Writing Matching Rule Plug-Ins
129
Need help?
Do you have a question about the NETSCAPE DIRECTORY SERVER 6.2 - PLUG-IN and is the answer not in the manual?
Questions and answers