X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=OGoContentStore%2FREADME;h=4c2b1d3b6afd3d3bfb2cf94fbd13e5ed4f62baad;hb=HEAD;hp=edfa572c98efd76345fe3ac6ae2bdabbfd5c57d7;hpb=9196e7bdff523bcfed373cd05b526cc71a09ace5;p=scalable-opengroupware.org

diff --git a/OGoContentStore/README b/OGoContentStore/README
index edfa572c..4c2b1d3b 100644
--- a/OGoContentStore/README
+++ b/OGoContentStore/README
@@ -1,5 +1,3 @@
-# $Id$
-
 Storage Backend
 ===============
 
@@ -15,6 +13,10 @@ Note: to sync with LDAP we need to periodically delete or archive old folders
 Folders have associated a type (like 'calendar') which defines the query
 attributes and serialization format.
 
+TODO
+====
+- hierarchies deeper than 4 (properly filter on path in OCS)
+
 Open Questions
 ==============
 
@@ -38,6 +40,33 @@ Class Hierarchy
   - field 'value' (eg array values for participants?)
   - BLOB archiver/unarchiver
 
+Defaults
+========
+
+  OCSFolderInfoURL - the DB URL where the folder-info table is located
+    eg: http://OGo:OGo@localhost/test/folder_info
+
+  OCSFolderManagerDebugEnabled      - enable folder-manager debug logs
+  OCSFolderManagerSQLDebugEnabled   - enable folder-manager SQL gen debug logs
+
+  OCSChannelManagerDebugEnabled     - enable channel debug pooling logs
+  OCSChannelManagerPoolDebugEnabled - debug pool handle allocation
+  
+  OCSChannelExpireAge       - if that age in seconds is exceeded, a channel 
+                              will be removed from the pool
+  OCSChannelCollectionTimer - time in seconds. each n-seconds the pool will be
+			      checked for channels too old
+  
+  [PGDebugEnabled] - enable PostgreSQL adaptor debugging
+
+URLs
+====
+
+  "Database URLs"
+  
+  We use the schema:
+    postgresql://[user]:[password]@[host]:[port]/[dbname]/[tablename]
+
 BLOB Formats
 ============
 
@@ -50,6 +79,24 @@ BLOB Formats
 - we need to parse the BLOB for different clients anyway (iCal != iCal ...)
 - XML: we could use some XML query extension to PG in the future?
 
+Update: we now have OCSiCalFieldExtractor
+  - it parses the BLOB as an iCalendar file and extracts a set of fixed
+    keys:
+    - title        - plain copy of "summary"
+    - uid          - plain copy
+    - startdate    - date as utime
+    - enddate      - date as utime
+    - participants - CNs of attendees separated by comma ", "
+    - location
+    - partmails
+    - sequence
+    - TBD: iscyclic
+    - TBD: isallday
+    - TBD: cycles  - I guess the client should fetch the BLOB to resolve
+  - the field extractor is accessed by OCSFolder using the folderinfo:
+    extractor = [self->folderInfo quickExtractor];
+    quickRow  = [extractor extractQuickFieldsFromContent:_content];
+
 Support Tools
 =============