thomas: doc/architecture freebusy.txt,1.21,1.22
cvs at kolab.org
cvs at kolab.org
Wed Apr 2 17:52:31 CEST 2008
Author: thomas
Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv29431
Modified Files:
freebusy.txt
Log Message:
typo cleanups (though "Specifiction" has a nice connotation)
Index: freebusy.txt
===================================================================
RCS file: /kolabrepository/doc/architecture/freebusy.txt,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- freebusy.txt 2 Apr 2008 15:42:42 -0000 1.21
+++ freebusy.txt 2 Apr 2008 15:52:29 -0000 1.22
@@ -81,11 +81,11 @@
information.
The following rules apply:
-1. We add to the Kolab Format Specifiction a new annotation which allows to
+1. We add to the Kolab Format Specification a new annotation which allows to
express this folder is freebusy relevant. (The annotation should
ideally also make that folder alarm relevant.)
-Existance of the annotation:
+Existence of the annotation:
for user folders: relevant for the fb of the owner
for group folders: relevant for the fbs of the people with read access
@@ -138,7 +138,7 @@
https://servername/freebusy/trigger/user1@domain.tld/calendar.pfb
https://servername/freebusy/trigger/group1@domain.tld/calendar.pfb
-We use SSL secured basic authentification for transfering the credentials to
+We use SSL secured basic authentication for transferring the credentials to
the server side code. The server side code then uses these credentials to
access the calendar folders and to write the pfbs.
@@ -184,7 +184,7 @@
to create the real freebusy list.
If a freebusy list is requested the script can just
-simply have to recursively get all pfb under the users fb cache hierachie
+simply have to recursively get all pfb under the users fb cache hierarchy
and then the ones in the group calendar folders which the user
can read and which are marked fb relevant.
@@ -204,15 +204,15 @@
https://servername/freebusy/trigger/X/PATH/FOLDERNAME.pfb
-After calling the pfb script the Kolab client may immediately delete the emtpy
+After calling the pfb script the Kolab client may immediately delete the empty
folder.
On the other hand the server side pfb creation script MUST be able to
-handle empty or unexisting calendar folders. A trigger call to an unexisting
+handle empty or not existing calendar folders. A trigger call to a not existing
or empty folder leads to deletion of any traces related to this folder in the pfb storage.
(*) It is the job of the pfb creation script to convert the UTF-8 encoded
-paths and folder names into the imapd specific nameing conventions.
+paths and folder names into the imapd specific naming conventions.
Future
------
@@ -224,7 +224,7 @@
else, but a unified freebusy list is wanted.
- - add referal type files for the cache hierachy that
+ - add referral type files for the cache hierarchy that
make the collector script search for an pfb elsewhere.
Advantage: Client could use other servers or local files for fb, too.
More information about the commits
mailing list