[cvs] [Wiki] changed: HordePolicy

[Ben Chavet]

ben  Wed, 24 May 2006 22:16:24 -0700

Modified page: http://wiki.horde.org/HordePolicy
New Revision:  1.24
Change log:  changed my mind on the "root" policy.

@@ -110,11 +110,10 @@
 ++ Other Thoughts
 
 * all $pref->getValue() calls could be handled on the backend by writing a Policy driver for the Prefs system, giving us a drop-in replacement.
 * we'd need a way to clearly define what happens if two Horde Policies have overlapping, conflicting settings.
-* there should be a default "root" policy, which cannot be detached from the root installation.  This policy would be a site-wide policy that always exists.
-* Should we keep a history of who created or edited a policy?  Can we use the history classes for this?
-* Do we need a Policy "manager" object like we have with the DataTree?  Or should we include static functions to Horde_Policy?  do static functions get copied for each instance of an object?  If so, the "manager" object might be the way to go.
+* Keep a history of who created or edited a policy, and when (maybe even track what changed).  Can we use the history classes for this?
+* Do we need a Policy "manager" object like we have with the !DataTree?  Or should we include static functions to Horde_Policy?  do static functions get copied for each instance of an object?  If so, the "manager" object might be the way to go.
 
 ----
 
 ++ API