[cvs] [Wiki] changed: HordePolicy

[Ben Chavet]

ben  Mon, 22 May 2006 19:35:26 -0700

Modified page: http://wiki.horde.org/HordePolicy
New Revision:  1.15
Change log:  decided on internal structure

@@ -6,47 +6,8 @@
 
 ----
 
 ++ Visualization of a Horde Policy
-
-<code>
-policy
-|-- name
-|-- date-updated
-|-- attribute-group
-|   |-- attributes
-|   |   |-- attribute1
-|   |   |   |-- value
-|   |   |   `-- scope
-|   |   `-- attribute2
-|   |       |-- value
-|   |       `-- scope
-|   `-- attribute-group
-|       |-- attribute-group
-|       |   `-- attribute1
-|       |       |-- value
-|       |       `-- scope
-|       `-- attribute1
-|           |-- value
-|           `-- scope
-|-- attribute-group
-|   `-- attribute1
-|       |-- value
-|       `-- scope
-`-- targets
-    |-- target1
-    `-- target2
-</code>
-
-* each app would have a policy.xml file defining what policy attributes are available.
-* A target can consist of one or more:
- * entire horde installation
- * horde group
- * individual user
- * guest user
- * OU if using LDAP backend
-
-Another internal structure idea:
 
 <code>
 policy
 |-- name
@@ -64,11 +25,17 @@
     `-- 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.
+* each app would have a policy.xml file defining what policy attributes are available.
+* A target can consist of one or more:
+ * entire horde installation
+ * horde group
+ * individual user
+ * guest user
+ * OU if using LDAP backend
 
-I'm leaning more toward the 2nd structure.
+This structure should be easy to cache when a given app is loaded.  something like {{ if (!isset($policy[$app])) { load $policy[$app] from xml } }}.
 
 ----
 
 ++ What would need to be done