[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: Operational attributes

So what does Sun do for plugins that implement custom attributes?

My personal preference in these cases is to keep the schema definitions
embedded in the code, to ensure that schema and code stay in sync. A separate
schema file is useless without the code that implements it, etc. etc...

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-devel@OpenLDAP.org
> [mailto:owner-openldap-devel@OpenLDAP.org]On Behalf Of Luke Howard

> I think we should allow operational attributes to be defined in slapd
> configuration files.
> In our application, we have a number of SLAPI plugins that compute
> operational attributes at search time. There is no easy way using the
> SLAPI plugin API to register the attribute types with the server, nor
> do other implementations of SLAPI expect this to be done.
> It would be nice to simply ship a schema file along with the plugin.
> I know there has been resistance to doing this in the past, and I
> understand the reasons why, but I'd be interested in any other
> thoughts.
> regards,
> -- Luke