[cvs] [Wiki] changed: HordePolicy

[Ben Chavet]

ben  Thu, 18 May 2006 21:30:52 -0700

Modified page: http://wiki.horde.org/HordePolicy
New Revision:  1.13
Change log:  save early, save often, right?

@@ -63,8 +63,12 @@
     |       `-- value
     `-- attribute3
         `-- value
 </code>
+
+This structure would be easier to cache when a given app is loaded.  something like {{ if (!isset($policy[$app])) { load $policy[$app] from xml } }}.  The other structure would either be messy to load per app, or would require loading all policy attributes for all apps at login.
+
+I'm leaning more toward the 2nd structure.
 
 ----
 
 ++ What would need to be done
@@ -108,9 +112,19 @@
 target_id
 target_type  <-- maybe
 </code>
 
-I'm not exactly sure how to throw the attribute-groups in here yet.
+I'm not exactly sure how to throw the attribute-groups in here yet.  Maybe, something like (taking some ideas from datatree here):
+
+<code>
+horde_policy
+------------
+policy_id
+policy_name
+policy_parent  <-- no need for all parents, just immediate parent
+</code>
+
+This would abstract the "policy" a bit and make them nestable in a tree.  So, attribute-group == policy for all practical purposes.  Problem is, a policy as a whole has a target, and attribute-groups would not have a target.  hmmm...
 
 ----
 
 ++ Cache