[cvs] [Wiki] changed: HordePolicy

[Ben Chavet]

ben  Tue, 23 May 2006 20:44:08 -0700

Modified page: http://wiki.horde.org/HordePolicy
New Revision:  1.18
Change log:  incorporate hooks into my train(s) of thought

@@ -69,8 +69,9 @@
 policy_id
 attribute_name
 attribute_scope
 attribute_overrideable
+attribute_hook
 attribute_value
 </code>
 
 <code>
@@ -98,8 +99,9 @@
 * 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?
+* Hooks should definitely come into play somehow.  Perhaps store the name of the hook function with the attribute, where there is no hook if this is null?
 
 ----
 
 ++ Links