1- de-IBM SLAPI
2- add a config statement, or redefine the dynamic backend one,
3  "modulepath", to set/modify the load path also for plugins
4  (both plugins and modules use ltdl, so "modulepath" suffices ...)
5- improve slapi logging (use some [v]s[n]printf function)
6- add a config statement to set the log file name, or better
7- use syslog where available?
8- add some plugin monitoring stuff in back-monitor (e.g. a subentry
9  for each plugin with data from struct Slapi_PluginDesc)
10- This is a very tough task: try to implement a sandbox to execute
11  plugins in, trap deadly signals and possibly disable unsafe plugins
12  without crashing slapd (fork from inside thread? trap signals
13  and longjump to next plugin execution? Brrr).
14
15---
16OpenLDAP: pkg/ldap/servers/slapd/slapi/TODO,v 1.4 2005/07/25 11:17:15 lukeh Exp
17