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

Re: Trigger registration with backend database!!!

I prefer perl backend to SLAPI for triggers as a concept. Comparing apples and oranges, but I think much of what is done with post/pre operational filters can be done with back-perl.

But I don't see it getting anywhere near the performance one would get with something like SLAPI. One problem is the construction/destruction of perl interpreters per thread, which often translates to per request. This can be changed by having the main thread keep an interpreter 'pool', and handing those out to separate threads, it would also remove the need to have a central lock for a single interpreter, as we do now. Hopefully these things can be investigated in the future.


Howard Chu wrote:
-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Kervin L.

Try the PERL backend.

There was talk about implementing netscape's SLAPI, but so far I haven't seen anything. http://www.openldap.org/lists/openldap-devel/200111/msg00124.html

I haven't seen anything new on this, I believe this effort has gone idle.
The OpenLDAP slapd API has changed pretty extensively from 2.0 to 2.1 and
it would be (believe it or not) a step backward in functionality to fit
Netscape SLAPI into the new framework. It is essentially impossible to
provide compatibility with the original Netscape definition, so there's
no plugin portability to be gained here.

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