martin: doc/architecture client_server.sgml,1.15,1.16

[cvs at intevation.de]

Author: martin

Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv9135/architecture

Modified Files:
	client_server.sgml 
Log Message:
Martin K.: Added documentation about the three-state freebusy annotation


Index: client_server.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/client_server.sgml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- client_server.sgml	20 Oct 2004 05:38:51 -0000	1.15
+++ client_server.sgml	25 Oct 2004 16:01:37 -0000	1.16
@@ -103,9 +103,9 @@
 
 <sect1><title> Vacation Functionality </title>
 <para>The vacation functionality is configured by the user via a simple
-webinterface available via HTTPS provided by the Kolab server or builtin SIEVE capabilities 
+webinterface available via HTTPS provided by the Kolab server or builtin SIEVE capabilities
 in the client. The actual vacation functionality is implemented on the server
-using Sieve (IETF RFC 3028). 
+using Sieve (IETF RFC 3028).
 A Free Software implementation of this scripting language
 for the Cyrus IMAP daemon is available.</para>
 <para>
@@ -226,17 +226,36 @@
 </para>
 <para>
 The relevance of a calendar folder is controlled by the presence of a free-busy
-annotation flag.  The availability of such a flag means that this folder shall
-be taken into account for the generation of the free-busy list.
+annotation flag and its value. The IMAP annotation is named <filename>/vendor/kolab/freebusy-relevant</filename>.
+The possible shared values are
+</para>
+<para>
+<itemizedlist mark='bullet'>
+<listitem><para>none</para>
+<para>
+This calendar folder is not relevant for the creation of freebusy data for anyone.
+</para>
+</listitem>
+<listitem>owner</para>
+<para>
+This calendar folder is relevant for the creation of freebusy data for owner only.
+</para>
+</listitem>
+<listitem>readers</para>
+<para>
+This calendar folder is relevant for the creation of freebusy data for everyone with read access.
+</para>
+</listitem>
+</itemizedlist>
 </para>
 <para>
 This allows a Kolab user to organize her calendaring by having many
 calendars folders in one account.
  </para>
 <para>
-Group calendars with the free-busy annotation set are taking into account for
-the free-busy lists for all Kolab users having read permissions on this calendar
-folder.
+Group calendars with the free-busy annotation (<filename>/vendor/kolab/freebusy-relevant</filename>) set and having the value
+of this IMAP annotation (<filename>value.shared</filename>) set to <filename>readers</filename> are taking into account for
+the free-busy lists for all Kolab users having read permissions on this calendar folder. This "push" semantic within a Kolab server domain is intentional and requires some cooperation between users.
 </para>
 <para>
 Conceptually this means that the administrators of the group account push the