[Kolab-devel] Closing Call: KEP #9

Georg C. F. Greve greve at kolabsys.com
Fri Sep 2 14:14:28 CEST 2011

On Friday 02 September 2011 09.11:18 Gunnar Wrobel wrote:
> 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

Good catch. I think that base64'ing should always be allowed.

There is the question though of whether we want too many different forms of 
serialization. Alain made a strong point of going for JSON encoding both in 
the initial discussion for ActiveSync configuration storage, as well as in the 
discussion for KEP #9.

I understand that JSON encoding would also be fully available for Horde, so 
switching to that might be a good idea.

But like I said in my previous mail, I think that KEPs should primarily be 
concerned with the Kolab namespace and we should not try to define what other 
groups or projects do internally.

So in my mind it would be better if Horde were also considering to switch to 
JSON, but that would not be a blocker for the KEP, IMHO. 

Best regards,

Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20110902/cd8ff58e/attachment.sig>

More information about the format mailing list