Table of Contents
Advertisement
Writing Plug-in Initialization Functions
Code Example 2-3
/* Set this information in the parameter block */
slapi_pblock_set( pb, SLAPI_PLUGIN_DESCRIPTION,
(void *)&mypdesc );
This example code specifies the following plug-in information:
•
The unique identifier for the server plug-in is
•
The vendor of the server plug-in is
•
The version of the server plug-in is
This version is intended to be used for your tracking purposes only; it is not
the same as the server compatibility version number specified by the
SLAPI_PLUGIN_VERSION
Compatibility," on page 43, for details on this parameter). As you make
changes to your plug-in code, you can track the version distributed using the
number contained in the
•
The description of the server plug-in is contained in the data structure value
sample pre-operation plug-in
Registering Your Plug-in Functions
Whether you register your plug-in through the initialization function depends
upon the type of function you are registering.
For some plug-in types, you do not need to register the plug-in function from
within the initialization function. For example, you register entry store and entry
fetch plug-ins by specifying the function names in the
dse.ldif
For other plug-in types, such as pre-operation plug-ins and post-operation
plug-ins, the Directory Server gets the pointer to your function from a parameter
in the initialization function parameter block. In these cases, you use the
slapi_pblock_set()
The full list parameters that you can use to register your plug-in functions are
listed in "Parameters for Registering Plug-in Functions," on page 566.
44
Netscape Directory Server Plug-in Programmer's Guide • October 2004
Specifying Plug-in Information (Continued)
parameter (see "Specifying Directory Server
Slapi_PluginDesc
file.
function to specify the name of your plug-in function.
test-plugin
.
example.com
.
0.5
structure.
.
plugin
.
directive in the
Advertisement
Table of Contents
