Autconfiguration for kolabclient

[Georg C. F. Greve]

Hi Sandro,

Would this auto config be available *before* or *after* authentication?

Identities in particular seem like something that ought to be available only 
afterward, and for Kolab Clients we might ultimately even want to store things 
such as Akonadi config so hooking up a new client becomes "magical."

To that end, we've already had some discussions, including a finished KEP for 
how it would be most useful to store configuration information on the server 
that several other functions are already using, see

http://wiki.kolab.org/KEP:9#Configuration_storage_in_XML_objects

Perhaps it would make sense to re-use this?

Best regards,
Georg


-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG				Make it your Kolab @ http://mykolab.com
Zürich, Switzerland				Swiss Secure Collaboration as a Service

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/20140604/149206ff/attachment.sig>