[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
cache-only backend
- To: openldap-software@OpenLDAP.org
- Subject: cache-only backend
- From: matthew sporleder <msporleder@gmail.com>
- Date: Sun, 22 May 2005 09:55:13 -0400
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Q9vin1epHRIlNuqRPpZJTKou3rMhMQmtzqa+4W4h8WeDRfQTi1DjURZZApKgSwd2Q+6svnPYVFtcE9R3tpCHQ4iT7cZDb9XonLJXOo2Mmf8WPIQ6FSPrAf0uy3NrdhQDXIVNFVKbGIJ17liMiVKvML3oNnCkjRgDtFIBVKzdzzs=
I was browsing through the backends for slapd and wondering if there
was anything like this:
Deploy a replica with no existing database,
Any searches not found in the local repository are searched from a set
of masters,
If found: cache response, return result,
Else if not found: return failure.
I can see this being beneficial as deploying (or fixing) replicas is
difficult with a large database, and could actually be very good at
keeping replicas up-to-date without a separate replication process
(depending on cache expire times, etc). I can also see this holding
some big disadvantages for the master servers having to provide tons
of information to populate these replicas.
--
_Matt