[Kroupware] Kroupware RFC

[Bo Thorsen]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 13 March 2003 19:23, Bernhard Reiter wrote:
> On Thursday 13 March 2003 09:55, Stephan Buys wrote:
> > I was just wondering if it would be a good idea to create an official
> > RFC around the collaboration features of Kroupware and Bynari.
> >
> > More specifically:
> > Formalise a method for storing contacts, notes and calendar events in
> > IMAP folders (ie. iCal encapsulated in MIME)
>
> I'm not sure in how far RFC 2445 -2447 already cover what you need.
> We do have the architecture document which is the reference document
> for Kolab right now. This should be a base and erfrakon is certainly
> happy if you suggest improvements.

I think what Stephan is proposing is to make a real RFC out of the part=20
that describes the storing of iCalendar files in emails.

> > Another idea would be to store FREE/BUSY information in LDAP so that
> > it becomes easier to look up this information in massive
> > organizations.
>
> LDAP should be used for information which are not written frequently.
> Thus I don't think it is a good idea to abuse LDAP for this.
> The current way seems very scalable to me as it just is a file lookup
> for apache. If needed it can be separated from the other servers and
> replicated.

He isn't suggesting to save the free/busy list with LDAP, just that the=20
URL where you can obtain the free/busy list is put in the address entry.=20
This would IMHO be really helpful. Example case: I'm on the company Kolab=20
server and my wife is on our own local one. How would we be able to find=20
each others free/busy lists? Answer: You can't, unless we both upload=20
them the same place - which would have to be the company one because=20
otherwise the others would not be able to find me. Now Kristina gets into=20
trouble because her working place has seen the light and are also running=20
Kolab... This can only be solved by having information about where the=20
contact is storing her free/busy list, and LDAP would suit that nicely.=20

But I'm still not implementing it in the client before 1.0 :-)

Bo.

=2D --=20

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

iD8DBQE+cPDfmT99lwfUS5IRAhx2AKCU4MByZpmZqP8L2s/3VltmtCe5hwCbBWAd
/DG/YDdCm90Pk9A5erjBllI=3D
=3DBn8e
=2D----END PGP SIGNATURE-----