[cvs] [Wiki] changed: HordePolicy

[Ben Chavet]

ben  Thu, 18 May 2006 21:21:53 -0700

Modified page: http://wiki.horde.org/HordePolicy
New Revision:  1.12
Change log:  more brainstorming

@@ -43,8 +43,28 @@
  * horde group
  * individual user
  * guest user
  * OU if using LDAP backend
+
+Another internal structure idea:
+
+<code>
+policy
+|-- name
+|-- targets
+|   |-- target1
+|   `-- target2
+|-- app1 (ie, imp)
+`-- app2 (ie, turba)
+    |--attribute-group1
+    |   |-- attribute-group2
+    |   |   `-- attribute1
+    |   |       `-- value
+    |   `-- attribute2
+    |       `-- value
+    `-- attribute3
+        `-- value
+</code>
 
 ----
 
 ++ What would need to be done
@@ -68,9 +88,8 @@
 horde_policy
 ------------
 policy_id
 policy_name
-policy_updated
 </code>
 
 <code>
 horde_policy_attributes
@@ -104,8 +123,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?
 
 ----
 
 ++ Links