Merge remote-tracking branch 'origin/master' into OPENLDAP_REL_ENG_2_5

[openldap] / TODO

diff --git a/TODO b/TODO
index e1f2329cf38ea11edac98d5b707bf9e8fc049bf7..b1c7a6047fa35d0f2f3701cbdd24aab49a54f19d 100644 (file)
--- a/TODO
+++ b/TODO
@@ -47,3 +47,15 @@ New syslog engine
 [12:46] <hyc> yes but the idea is still based on numbered substitution parameters
 [12:47] <hyc> it's a pretty obvious approach, and with regex, time-tested.
 [12:48] <hyc> I may try to sneak it into OpenLDAP 2.5
+
+
+Overhaul overlays and backends, see ITS 6166, ITS6531
+
+(In relation to a discussion about slapo-chain)
+<hyc> anyway, the nicer ting to fix would be in 2.5, push all of the repl consumer code into its own overlay
+<hyc> in that case, updateref would be processed wherever the overlay was configured
+<hyc> so no longer tied to the frontend
+<hyc> 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)
+<hyc> I would think we can get rid of the update ref directive entirely, just point all writes to that consumer's provider.
+
+Update dynlist so it works with search filters, so that autogroup can be deleted