From 111d7f4b29517885b9b0d3f4f0764a9309c3cc0f Mon Sep 17 00:00:00 2001 From: Gavin Henry Date: Sat, 9 Feb 2008 22:20:20 +0000 Subject: [PATCH] Wee update. --- doc/guide/admin/overlays.sdf | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/doc/guide/admin/overlays.sdf b/doc/guide/admin/overlays.sdf index 209be6177a..7f6f50e011 100644 --- a/doc/guide/admin/overlays.sdf +++ b/doc/guide/admin/overlays.sdf @@ -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 -- 2.39.5