No subject

absolutely certain if this should rather be

 kolab.h-prefs

In any case this folder type will be used to store client preferences,
specifically the Horde preferences. So far Horde used the Kolab LDAP
tree for that but this led to the known problems of including the
Horde LDAP schema in the Kolab server. There were also problems with
the Kolab web admin when using the LDAP based preference system. In
addition it is probably not the most appropriate storage location
since the preferences in Horde are bound to be changed rather often
while a user works in Horde.

As a consequence I would like to store the Horde preferences in a
dedicated "Preferences" folder on the IMAP server.

A draft patch for that would be ready and works fine:

http://hg.pardus.de/cgi-bin/hg.cgi/horde/HORDE_CVS/file/tip/framework/HK-GW-Prefs-Kolab_IMAP.patch

So my main question is if it okay to declare this new folder type.

This would of course mean that I'd feel tempted to continue declaring
more folders types such as h-links, h-filter, h-bugs, etc. These all
represent existing Horde applications that simply need storage space
(other than the default SQL storage). But I think I remember there was
some opposition concerning the idea of storing additional data types
on the server :)

Waiting for comments!

Cheers,

Gunnar

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 40 432 72335                           Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~