-# $Id$
-
Storage Backend
===============
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
==============
- 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
=============