bernhard: doc/architecture freebusy.txt,1.24,1.25

[cvs at kolab.org]

Author: bernhard

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

Modified Files:
	freebusy.txt 
Log Message:
* Clarified what constitutes an operation after which a client must trigger.
* Typo fixed.


Index: freebusy.txt
===================================================================
RCS file: /kolabrepository/doc/architecture/freebusy.txt,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- freebusy.txt	25 Sep 2008 09:23:40 -0000	1.24
+++ freebusy.txt	14 Oct 2008 12:59:14 -0000	1.25
@@ -176,13 +176,16 @@
 One successful trigger does both.
 
 In general all clients writing to calendar folders on the server
-must trigger the generation of pfbs. This include KDE Kontact,
+must trigger the generation of pfbs. This includes KDE Kontact,
 the Outlook Clients, the web client and the resource manager.
 They must trigger after one or more write operations to one folder.
 If a clients knows that it will do several write operations
 during a very short interval to one folder,
 it should delay the trigger until it has done the operations
 to avoid unnecessary triggers.
+Creation, deletion of a folder, 
+change of ACLs, annotations or non-local flags 
+also constitute a "write operation" making a trigger recessary.
 
 Pfb collector