Note that this article was written five years ago, and the code here will probably not work correctly with the new Fedora release of Directory Server. I will update this article and code examples as soon as I can possibly can, after I've finished playing with the DS installation on my dev-box.

Part 1: Overview of the API and Writing a Simple Plug-In

By writing a Netscape Directory Server extension ("plug-in"), you can extend the server's capabilities in a number of different ways. For example, you can validate data before it's stored in the directory, notify users when data in the directory changes, or replace the existing database with your own database. A plug-in is a shared object or library (or, on Windows NT, a dynamic link library) containing your own functions. Plug-ins are called by the server when specific events occur, such as before an LDAP add operation is performed.