[cvs] [Wiki] changed: HordePolicy

[Ben Chavet]

ben  Thu, 18 May 2006 19:16:32 -0700

Modified page: http://wiki.horde.org/HordePolicy
New Revision:  1.11
Change log:  add attribute-groups into the mix

@@ -11,13 +11,26 @@
 <code>
 policy
 |-- name
 |-- date-updated
-|-- attributes
-|   |-- attribute1
-|   |   |-- value
-|   |   `-- scope
-|   `-- attribute2
+|-- 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
@@ -46,9 +59,9 @@
 ++ Storage
 
 In order to make Horde Policies as generic as possible, it's probably best to specify a new backend for them.  Then we can write policy drivers for the various parts of Horde that might use them, such as Prefs.
 
-I'm a big fan of the Datatree structure, slightly simplified, to hold the Policy information.  The DataTree itself has proved not to scale very well, but I think by removing a few unneeded fields (for this application, at least), we can reduce the number of JOIN statements, and it should scale just fine.  Another thing to think about is how many Horde Policies is a given site going to have?  Probably no more than a handful on average.
+I'm a big fan of the Datatree structure, slightly simplified, to hold the Policy information.  The !DataTree itself has proved not to scale very well, but I think by removing a few unneeded fields (for this application, at least), we can reduce the number of JOIN statements, and it should scale just fine.  Another thing to think about is how many Horde Policies is a given site going to have?  Probably no more than a handful on average.
 
 Anyway, here's a new table structure idea:
 
 <code>
@@ -75,8 +88,10 @@
 policy_id
 target_id
 target_type  <-- maybe
 </code>
+
+I'm not exactly sure how to throw the attribute-groups in here yet.
 
 ----
 
 ++ Cache