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

Re: Hardcode "description" and "seeAlso"


I do not know details about hard-coded schema elements in OpenLDAP. But
I'd like to raise a short discussion about it. To me hard-coded schema
elements are generally something to avoid.

My rather naive suggestion is rather than hard-coding all the schema
elements ever needed by a backend into OpenLDAP all these backends and
overlays should lookup required schema elements in the currently schema
config set by the directory admin and fail to start (or just log) if
they are not present.

As I said I have no overlook about the implications with upcoming
back-config etc.

Ciao, Michael.

Pierangelo Masarati wrote:
> I'm consistently using "description" and "seeAlso" in back-monitor to
> present the description of what an entry is monitoring and to represent
> loose relationships between entries.  I think their usage is appropriate,
> and I'd prefer to avoid defining a "monitorDescription" and
> "monitorSeeAlso"; this suggests the opportunity to hardcode these
> well-known and standard track definitions, taking advantage of the jump
> between 2.2 and 2.3, because the need to define monitor schema __after__
> core.schema is loaded, and pending the definition of these attributes, is
> limiting the versatility of back-monitor, significantly on the side of its
> customization by dynamic modules.  See also
> <http://www.openldap.org/lists/openldap-devel/200504/msg00106.html>.
> Objections?
> p.