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

Re: Trigger registration with backend database!!!

Howard Chu wrote:
Good idea. You could write a script for back-perl or back-shell to watch the

You can't do pre-operation plugins with this method. Say I would like to reject any modify operations if a certain attribute were changed to a certain value, but allow others.

replog and return the results to you. There is currently no explicit control
that enables persistent search in OpenLDAP but you can do this yourself in
how you write your script's search function. back-perl with a single global
interpreter would be the most efficient approach.

How so? Say we have 10 simultaneous connections, they all have to wait on a single interpreter.

Please, correct me if I'm wrong on this.


  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support


-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Jatin Nansi
Sent: Tuesday, April 23, 2002 11:20 PM
To: shassingh@hss.hns.com; openldap-software@OpenLDAP.org
Subject: Re: Trigger registration with backend database!!!


One way in which i think you could do this:
Configure replication, and keep a watch on the replog.
you need not have any server to replicate to, but u will
get a perfect idea of what has changed as soon as it changes.

Jatin

On Wednesday 24 April 2002 09:32, shassingh@hss.hns.com wrote:

Hi,
           I am using OpenLdap 2.0.23 package. I am using libraries
provided by OpenLdap. My client needs
to get a trigger whenever some external agent makes some changes to the
directory. Is there any way this can be done?
Is persistent search currently supported by OpenLdap 2.0.23?


Thanx
Shashi




"DISCLAIMER: This message is proprietary to Hughes Software 

Systems Limited

(HSS) and is intended solely for the use of the individual to 

whom it is

addressed. It may contain  privileged or confidential information  and
should not be circulated or used for any purpose other than for


what it is

intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying,


altering, or

disclosing the contents of this message. HSS accepts no 

responsibility for

loss or damage arising from the use of the information 

transmitted by this

email including damage from virus."