[Kolab-devel] Re: Where do we start?

Bo Thorsen bo at sonofthor.dk
Thu May 15 08:26:43 CEST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 15 May 2003 14:17, Stephan Buys wrote:
> > > 3) What about splitting the Kolab schema files out to different
> > > files again? I would like to add support for 2739 (LDAP Free/Busy
> > > URI's) to the server so that the client-side guys can start playing
> > > with it. (This of course does not affect the kolab.schema file, I
> > > just think it is easier to manage the different Schema files
> > > seperately)
> >
> > I know about RFC 2739 but what do you expect to gain from putting the
> > Free/Busy information into LDAP?
>
> Not the Free/Busy information but a URI to the Free/Busy information.
> I can think of several advantages for future client development. It
> will be easy to find Free/Busy information accross different
> organizations and when using several aliases. (ie Free/Busy is not as
> hap-hazard as using the %NAME% portion of an email address).
>
> This obviously does not affect Clients like Outlook but can set the
> benchmark for future KMail as well as other clients. You will not be
> restricted to a single Free/Busy repository but will be able to use
> several in different organizations.
>
> IMHO it just "feels right?"

This is something we have discussed before on the kroupware at kde.org list, 
and IIRC the general opinion was that it would be necessary to have this 
at some point. Especially for people with connection to two different 
kolab servers, this is simply essential.

Bo.

- -- 

     Bo Thorsen                 |   Praestevejen 4
     Senior Software Engineer   |   5290 Marslev
     Klarälvdalens Datakonsult  |   Denmark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+wzMjmT99lwfUS5IRAun+AJsGCZoPxt/ji+TcRKba2u2aO4hc8QCaAztU
9o9VlhAn9pIiz4cY2MnrJO4=
=Tj09
-----END PGP SIGNATURE-----




More information about the devel mailing list