upstream/openldap
1
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-12-26 17:49:59 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Wee update.

Browse source
This commit is contained in:
Gavin Henry 2008-02-09 22:20:20 +00:00
parent 4b97ecd0fd
commit 111d7f4b29
1 changed files with 18 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/guide/admin/overlays.sdf
View file

@ -347,9 +347,24 @@ H2: Dynamic Directory Services
H3: Overview
This overlay supports dynamic objects, which have a limited life after
which they expire and are automatically deleted.
The {{dds}} overlay to {{slapd}}(8) implements dynamic objects as per RFC 2589.
The name {{dds}} stands for Dynamic Directory Services. It allows to define
dynamic objects, characterized by the {{dynamicObject}} objectClass.
Dynamic objects have a limited lifetime, determined by a time-to-live (TTL)
that can be refreshed by means of a specific refresh extended operation. This
operation allows to set the Client Refresh Period (CRP), namely the period
between refreshes that is required to preserve the dynamic object from expiration.
The expiration time is computed by adding the requested TTL to the current time.
When dynamic objects reach the end of their lifetime without being further
refreshed, they are automatically {{deleted}}. There is no guarantee of immediate
deletion, so clients should not count on it.
Dynamic objects can have subordinates, provided these also are dynamic objects.
RFC 2589 does not specify what the behavior of a dynamic directory service
should be when a dynamic object with (dynamic) subordinates expires.
In this implementation, the lifetime of dynamic objects with subordinates is prolonged
until all the dynamic subordinates expire.
H3: Dynamic Directory Service Configuration