From: Quanah Gibson-Mount Date: Thu, 11 Feb 2016 17:51:27 +0000 (-0600) Subject: Add an example of how things change once ITS6166 is done X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=3e2409d4c22883d5a00e0df9d3e6c4605b4776c3;p=openldap Add an example of how things change once ITS6166 is done --- diff --git a/TODO b/TODO index e588f3e264..a941328e45 100644 --- a/TODO +++ b/TODO @@ -50,3 +50,10 @@ New syslog engine Overhaul overlays and backends, see ITS 6166 + +(In relation to a discussion about slapo-chain) + anyway, the nicer ting to fix would be in 2.5, push all of the repl consumer code into its own overlay + in that case, updateref would be processed wherever the overlay was configured + so no longer tied to the frontend + it would also make it more feasible to have multiple different consumer configs in a single DB, each with their own provider URL (and thus their own updateref) + I would think we can get rid of the update ref directive entirely, just point all writes to that consumer's provider.