bernhard: doc/architecture freebusy.txt,1.22,1.23

cvs at kolab.org cvs at kolab.org
Tue Jun 17 09:13:57 CEST 2008


Author: bernhard

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

Modified Files:
	freebusy.txt 
Log Message:
Removed the status Draft line as this is not draft anymore since a long time.
Change phrasing to make sure that invitations MAY also be accepted for other
than the default folder.
Some minor reformatting to fit 80 chars width.


Index: freebusy.txt
===================================================================
RCS file: /kolabrepository/doc/architecture/freebusy.txt,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- freebusy.txt	2 Apr 2008 15:52:29 -0000	1.22
+++ freebusy.txt	17 Jun 2008 07:13:55 -0000	1.23
@@ -1,5 +1,4 @@
 How to handle freebusy lists for Kolab2
-Draft
 Principal authors: Martin Konold, Bernhard Reiter
 $Id$
 
@@ -32,7 +31,8 @@
 User folder Calendars
 
 A user may have several personal folders in his account. One Folder is called
-the default folder. The default folder is used when accepting invitations.
+the default folder. The default folder is usually used 
+when accepting invitations automatically.
 
 The structure of user calendar folders is like
 
@@ -43,9 +43,10 @@
 
 Group Calendars
 
-A group may have several calendars (often only one). Technically a group
-calendar is just a special user account with more than one user having access
-permissions. A group as opposed to a user shall be used to give
+A group account may have several calendar folders (often only one). 
+Technically a group calendar is just a special user account 
+with more than one user having access permissions. 
+A group as opposed to a user shall be used to give
 folders to several users on an equal level. Each folder has an admin,
 which is the person which can give out rights to the folders.
 
@@ -128,8 +129,9 @@
 If a calendar folder is removed the corresponding pfb must also be removed.
 
 Actually the term pfb cache is a little bit misleading as it actually is an
-intermediate store which does not only cache the results of pfb trigger processes
-but which implicitly also defines which pfbs are relevant to create the user specific fb.
+intermediate store which does not only cache the results of pfb trigger 
+processes but which implicitly also defines which pfbs are relevant 
+to create the user specific fb.
 
 Triggering pfb
 





More information about the commits mailing list