bernhard: doc/architecture freebusy.txt,1.16,1.17

[cvs at intevation.de]

Author: bernhard

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

Modified Files:
	freebusy.txt 
Log Message:
Clarification: Tried to make the paths look more like real cyrus path
	so that it matches the output of cyradm listmailboxes better.

	* Added a "user/" prefix to the user and group paths
	* changed shared/x to shared.x, because this is how Cyrus does it.^

Fixed one typo.


Index: freebusy.txt
===================================================================
RCS file: /kolabrepository/doc/architecture/freebusy.txt,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- freebusy.txt	14 Jun 2005 20:18:52 -0000	1.16
+++ freebusy.txt	30 Jun 2005 15:19:29 -0000	1.17
@@ -36,10 +36,10 @@
 
 The structure of user calendar folders is like
 
-user1/calendar (1, fb, default)
-user1/private/calendar (2)
-user1/anotherhierarchy/calendar (3, fb)
-user1/yetanotherhierarchy/calendar (4, fb)
+user/user1/calendar (1, fb, default)
+user/user1/private/calendar (2)
+user/user1/anotherhierarchy/calendar (3, fb)
+user/user1/yetanotherhierarchy/calendar (4, fb)
 
 Group Calendars
 
@@ -49,10 +49,10 @@
 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.
 
-group1/calendar (1, fb)
-group1/myhierarchie/calendar (2)
-group2/myhierarchie/calendar (3, fb)
-group2/otherhierarchy/calendar (4)
+user/group1/calendar (1, fb)
+user/group1/myhierarchie/calendar (2)
+user/group2/myhierarchie/calendar (3, fb)
+user/group2/otherhierarchy/calendar (4)
 
 Multi-Group Calendars
 
@@ -66,10 +66,10 @@
 of them have to be at an event. E.g. it is better to work with invitations
 or a more specific group folder when wanting half of the company to a meeting.
 
-shared/calendar (1)
-shared/ahierarchie/calendar (2)
-shared/anotherhierarchy/calendar (3)
-shared/yetanotherhierarchy/calendar (4)
+shared.calendar (1)
+shared.ahierarchie/calendar (2)
+shared.anotherhierarchy/calendar (3)
+shared.yetanotherhierarchy/deeper/calendar (4)
 
 
 Partial fb
@@ -87,17 +87,17 @@
 
 Existance of the annotation:
 	for user folders: relevant for the fb of the owner
-	for group folders: relevtant for the fbs of the people with read access
+	for group folders: relevant for the fbs of the people with read access
 
 
 E.g. in the notation and the example above we have fb flags
 on the following folders:
 
-user1/calendar (1, fb)
-user1/anotherhierarchy/calendar (3, fb)
-user1/yetanotherhierarchy/calendar (4, fb)
-group1/calendar (1, fb)
-group2/myhierarchie/calendar (3, fb)
+user/user1/calendar (1, fb)
+user/user1/anotherhierarchy/calendar (3, fb)
+user/user1/yetanotherhierarchy/calendar (4, fb)
+user/group1/calendar (1, fb)
+user/group2/myhierarchie/calendar (3, fb)
 
 If a client changes the contents of one of those calenders, 
 it must trigger the creation of the pfb and xpdf as described below.