RE: asynchronous event notification

[Gary Williams <Gary.Williams@sas.com>]

JNDI implements an interface to LDAP V2 (or V3) and as such is
able to interface to OpenLDAP(V1.x or V2.0).  As far as receiving
events from an LDAP server, RFC 2589 addresses this, but I'm not
aware of which servers (if any) actually implement it.  I'd be very
interested to hear if someone knows for sure which ones do or
are planning to.

> -----Original Message-----
> From: Howard Chu [mailto:hyc@highlandsun.com]
> Sent: Monday, December 20, 1999 9:48 AM
> To: David J. Ferrero; openldap-software
> Subject: RE: asynchronous event notification
> 
> 
> > -----Original Message-----
> > From: owner-openldap-software@OpenLDAP.org
> > [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of David J.
> > Ferrero
> > Sent: Monday, December 20, 1999 6:28 AM
> > To: openldap-software
> > Subject: asynchronous event notification
> >
> >
> > I'm working on a OpenLdap/JNDI application and had plans to 
> register for
> > namespace and object content change events (add, remove, rename,
> > change). Ie: I'd like for the application to be notified when a new
> > entry is made to openldap or removed or changed or renamed. From a
> > cursory scan through JNDI: javax.naming.event.* and 
> javax.naming.ldap.*
> > packages it appears that these are LDAP v3 features and 
> probably doesn't
> > exist in OpenLDAP 1.X but maybe would be available in OpenLDAP 2.X
> >
> > Could someone with more intimate knowledge of LDAP v2 vs. 
> v3 spec and
> > OpenLDAP development or JNDI w/OpenLDAP care to comment on 
> above with
> > regard to registering for unsolicated events and asynchronous event
> > notifications?
> >
> > I could probably just as easily develop another form of 
> communication
> > between the producer and consumer applications but would 
> rather use LDAP
> > events if available.
> >
> > Any quick response is appreciated as this is under development now.
> > Regards,
> > David Ferrero
> >
> 
> I vaguely recall reading a proposed extension to LDAPv3 for 
> this feature,
> but can't find the document reference at the moment. It's not 
> present in
> OpenLDAP 2.x (yet - someone with sufficient inspiration could 
> always add
> it). The typical way one would go about adding such a feature 
> would be to
> have the client issue a search request to a special DN, which 
> the server
> provides for this purpose. Whenever a desired event occurs, a 
> search entry
> is sent back to the client. The search operation is never 
> terminated by the
> server, it is left pending until the client explicitly 
> abandons it. In the
> meantime, entries are sent back as events occur.
> 
>   -- Howard Chu
>   Chief Architect, Symas Corp.       Director, Highland Sun
>   http://www.symas.com               http://highlandsun.com/hyc
>