Processing An Ldap Search Operation - Netscape DIRECTORY SERVER 7.0 - PLUG-IN Manual

Processing an LDAP Search Operation

• The
unbind
• The
unbind
You set these parameters to the names of your functions by calling
slapi_pblock_set()
Your plug-in functions should return
returns a non-zero value, the post-operation unbind function is never called.
Processing an LDAP Search Operation
The server processes an LDAP search operation in two stages:
• First, the server gets a list of candidate entries, using an index (if applicable).
For example, for a search filter that finds entries where
checks the index for the
start with
If no applicable index exists, all entries are considered to be candidates.
To get the list of candidates, the server calls the backend search function. For
details, see "Getting the List of Candidates," on page 91.
• Next, the server iterates through each candidate in the list and determines if
the candidate matches the search criteria.
If an entry matches the criteria, the server sends the entry to the client.
To check each candidate, the server calls the backend
function for each candidate in the list. For details, see "Iterating through
Candidates," on page 92.
The rest of this section explains these stages in more detail.
90 Netscape Directory Server Plug-in Programmer's Guide • October 2004
SLAPI_PLUGIN_PRE_UNBIND_FN
function.
SLAPI_PLUGIN_POST_UNBIND_FN
function.
.
mail
, and generates a list of matching entries.
a
parameter specifies the pre-operation
parameter specifies the post-operation
if successful. If the pre-operation function
0
attribute (if the index exists), finds the keys that
, the server
mail=a*
next candidate