martin: doc/architecture freebusy.txt,1.13,1.14
cvs at intevation.de
cvs at intevation.de
Mon Jun 13 19:37:19 CEST 2005
- Previous message: martin: server/imap Makefile, NONE, 1.1 README, NONE, 1.1 imap.annotate.patch, NONE, 1.1 kolab.patch, NONE, 1.1
- Next message: martin: doc/architecture freebusy.txt,1.14,1.15
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: martin
Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv19042/architecture
Modified Files:
freebusy.txt
Log Message:
Martin Konold: Add support for deleting calendar folders with nice cleanup. Add support for alias instead of
primary email address (helps for migrations and renameings of mailboxes)
Index: freebusy.txt
===================================================================
RCS file: /kolabrepository/doc/architecture/freebusy.txt,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- freebusy.txt 15 Feb 2005 11:01:52 -0000 1.13
+++ freebusy.txt 13 Jun 2005 17:37:17 -0000 1.14
@@ -154,7 +154,8 @@
b) the uid
c) the corresponding imap patch component of the user name
(the server will try to add @maildomain to it.)
- and PATH and FOLDERNAME being UTF-8 encoded IMAP foldernames.
+ and PATH and FOLDERNAME being UTF-8 encoded IMAP foldernames.
+ d) any valid email alias
All pfbs are readable for every (authenticated) user
though normal users don't require to read the pfbs
@@ -188,14 +189,24 @@
https://servername/freebusy/group1@domain.tld.ifb
https://servername/freebusy/user1@domain.tld.xfb
+Deletion of Calendar folders
+
+When deleting a calendar folder a Kolab client must first delete all
+appointments on the server and then immediately call the pfb script
+
+ https://servername/freebusy/trigger/X/PATH/FOLDERNAME.pfb
+
+After calling the pfb script the Kolab client may immediately delete the emtpy
+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
+or empty folder leads to deletion of any traces related to this folder in the pfb storage.
+
Future
------
For the future scheme could eventually be extend towards:
-
- - make it possible for clients to upload the pfb instead
- of just triggering the creation.
- Advantages: Put load on the client.
- add referal type files for the cache hierachy that
make the collector script search for an pfb elsewhere.
- Previous message: martin: server/imap Makefile, NONE, 1.1 README, NONE, 1.1 imap.annotate.patch, NONE, 1.1 kolab.patch, NONE, 1.1
- Next message: martin: doc/architecture freebusy.txt,1.14,1.15
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the commits
mailing list