[Date Prev][Date Next]
More efficient way to represent local+remote views?
- To: firstname.lastname@example.org
- Subject: More efficient way to represent local+remote views?
- From: Kartik Subbarao <email@example.com>
- Date: Tue, 17 Jul 2012 10:24:54 -0400
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
I'm currently using the following configuration for an
application-specific LDAP directory to present a unified view of its
local data (ou=localapp) and remote data (ou=people), all under
The idea being that clients of this directory can simply set the base DN
to dc=example,dc=com without needing to know which parts are local and
which parts are pulled in remotely.
My understanding is that this approach incurs some overhead in going
through the ldapi interface for each operation that ends up being
performed on the local backend. Is it possible to eliminate that
overhead through an alternate approach? I looked at back_relay, but
couldn't get it to do what I wanted. I don't want to rewrite any of the
suffixes -- I just want it to do exactly as above in the back-meta
configuration, but replace "ldapi:///" with "internal-backend-api:///",
as mentioned in this part of the back-relay docs: "back-relay bypasses
the real database frontend operations by short-circuiting operations
through the internal backend API".