Subject: LDAP Persistent Search Control Protocol -- Request
Author: SteveHB
In response to: LDAP Persistent Search Control
Posted on: 09/14/2006 08:57:45 PM
The control sent to server may be included in the Controls portion of an LDAPv3 SearchRequest message, as defined in Section 4.1.12 of [LDAPv3]. The structure of this control is as follows:
PersistentSearchControl ::= SEQUENCE {
controlType 2.16.840.1.113730.3.4.3,
criticality BOOLEAN DEFAULT FALSE,
controlValue persistentSearchControlValue
}
The persistentSearchControlValue is an OCTET STRING wrapping the BER-encoded
version of the following SEQUENCE:
persistentSearchControlValue::= SEQUENCE {
changeTypes INTEGER,
-- add(1)|delete(2)|modify(4)|modDN(8)
changesOnly BOOLEAN,
returnECs BOOLEAN
}
>
> On 09/14/2006 03:16:43 PM
SteveHB wrote:
http://www3.ietf.org/proceedings/01mar/I-D/ldapext-psearch-03.txt
This document defines two controls that extend the LDAPv3 [LDAP] search operation to provide a simple mechanism by which an LDAP client can receive notification of changes that occur in an LDAP server. The mechanism is designed to be very flexible yet easy for clients and servers to implement.
The approach taken by the Persistent Search mechanism described in this document is to alter the standard LDAP search operation so that it does not end after the initial set of entries matching the search criteria are returned. Instead, LDAP servers keep the search operation going. This provides clients and servers participating in Persistent Search with an active channel through which entries that change (and additional information about the changes that occur) can be communicated.
References:
