[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#5330) back-null upgrade
h.b.furuseth@usit.uio.no wrote:
> Full_Name: Hallvard B Furuseth
> Version: HEAD
> OS:
> URL:
> Submission from: (NULL) (129.240.6.233)
> Submitted by: hallvard
>
>
> I'll be upgrading back-null a bit. At the moment just support for
> Back-config, Modify-Increment Extension and empty rootpw.
> Maybe grow it to a useful template of a nontrivial backend later
> (after I learn how to write that), with access control, referrals,
> various extensions... Might be almost-unused and thus subject to
> code rot, but less so than documentation of the backend API.
>
> However I imagine that could slow it down somewhat, so it might
> become less useful when used to benchmark backends. (E.g. if you
> run a test with some backend, then with back-null, diff the time
> to see how much was spent in the backend.)
I don't believe back-null should ever handle access controls or referrals. It
shouldn't have any config options at all, really. Create some other backend if
you want a dummy template that shows how all the other APIs are tied in.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/