martin: doc/architecture client_server.sgml,1.18,1.19

[cvs at intevation.de]

Author: martin

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

Modified Files:
	client_server.sgml 
Log Message:
Martin K.: Even better wording as discussed with david. (Thanks!)


Index: client_server.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/client_server.sgml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- client_server.sgml	25 Oct 2004 19:51:18 -0000	1.18
+++ client_server.sgml	25 Oct 2004 20:11:35 -0000	1.19
@@ -231,7 +231,7 @@
 </para>
 <para>
 <itemizedlist mark='bullet'>
-<listitem><para>none</para>
+<listitem><para>nobody</para>
 <para>
 This Kolab folder is not relevant for the creation of freebusy and alarm data for anyone.
 </para>
@@ -258,17 +258,17 @@
 calendars folders in one account.
  </para>
 <para>
-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
+Group calendars with the free-busy annotation (<filename>/vendor/kolab/incidences-for</filename>) set and having the value
+of this IMAP annotation (<filename>value.shared</filename>) set to <filename>readers</filename> are taken 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
-free-busy relevants on the Kolab users by means of granting them read access.
+free-busy relevance on the Kolab users by means of granting them read access.
 </para>
 
 <para>Support for insecure FTP and HTTP protocols to upload and download
-free-busy lists is discouraged for Kolab 2.
+free-busy lists is discouraged for Kolab 2. Users are adviced to use https instead.
 </para>
 <para>
 For the future upload capability of private local free-busy information to the