[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
search mechanism in openldap
- To: OpenLDAP-software@OpenLDAP.org
- Subject: search mechanism in openldap
- From: "Kamal R. Prasad" <kamalp@acm.org>
- Date: Wed, 31 May 2006 19:58:00 +0530
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=fetDdU2VYJI37gxkqpzBjnXYLHyqKZoCYNU0GYfMJssZXoJU1me2wfaoN9mTTr4l6VHs12Fr71yIwy4MqbbqgYuiCzNnx4vM8cnILGtdJH2t+sPbCvC0Ef4LcWTVU3kmAoJxyRhOUmrri9G2qHZgMmuQL7e8Q3mGQY7hnQ1KHSY=
Hello,
I am working on a software that wishes to generate hierarchial information
from a relational database. It is also supposed to accept queries like (get
me objevt from this tree AND this tree) or (get me object with attribute
value = X and object with attrval = Y).
I found that openldap already has this functionality. However, I have no
requirement for the data to be accessed across machines as the ldap protocol
enables. Is there anyway one can bypass the ldap server to achieve this
functionality -or where exactly is this functionality present?
Does openldap optimize searches in some way? Who exactly handles the
searches when a client sends in a request? is it slapd or berkeley db4? What
is the performance overhead of running slapd on the same box just to get
this functionality?
thanks
-kamal