[Kolab-devel] Closing Call: KEP #9
Jeroen van Meeuwen (Kolab Systems)
vanmeeuwen at kolabsys.com
Fri Sep 2 11:51:15 CEST 2011
Gunnar Wrobel wrote:
> Quoting "Jeroen van Meeuwen (Kolab Systems)" <vanmeeuwen at kolabsys.com>:
> > Hello,
> > I would like to announce the closing call stage for KEP #9, a design KEP
> > on storage of configuration and application control information;
> > http://wiki.kolab.org/index.php?title=User:Greve/Drafts/KEP:9&oldid=117
> > 06
> "Where array serialization or hashing is required because a value
> cannot be stored as plain text or contains illegal characters, values
> Notation (JSON).
> No other encoding MUST be used."
> Looking at what we currently support in
> /kolab/etc/imapd/imapd.annotation_definitions most values comply with
> this requirement. There are exceptions though:
> 1) /vendor/kolab/activesync: base64 encoded JSON serialization
> 2) /vendor/horde/share-params: base64 encoded PHP serialization
I have no objections against allowing a hashed / serialized object to be
> I'm uncertain about what gets stored in "/vendor/tarent/syncpref" and
> "/vendor/x-toltec/test". "/vendor/kolab/h-share-attr-desc" is most
> likely unused (though I would have to check when and why it was
> exactly added).
I feel we need another (few) informational KEP(s) to explain the other
annotations currently deployed through Kolab.
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the format