steffen: doc/architecture freebusy.txt,1.2,1.3

cvs at intevation.de cvs at intevation.de
Tue Sep 28 15:32:26 CEST 2004


Author: steffen

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

Modified Files:
	freebusy.txt 
Log Message:
information about the specific URLs to use for freebusy info

Index: freebusy.txt
===================================================================
RCS file: /kolabrepository/doc/architecture/freebusy.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- freebusy.txt	22 Sep 2004 16:24:06 -0000	1.2
+++ freebusy.txt	28 Sep 2004 13:32:24 -0000	1.3
@@ -114,13 +114,21 @@
 
 On the server we use mod_rewrite to parse URLs like (needs more thought!)
 
-https://servername/group1/group1/calendar.pfb
-https://servername/group1/group1/calendar.pfb
+https://servername/freebusy/user1@domain.tld/user1@domain.tld/calendar.pfb
+https://servername/freebusy/user1@domain.tld/group1@domain.tld/calendar.pfb
 
 We use SSL secured basic authentification for transfering the credentials to 
 the server side code. The server side code then uses these credentials to 
 access the calendar folders and to write the pfb.
 
+To trigger creation of a pbf, issue a HTTP GET request to
+
+https://servername/freebusy/trigger/user1@domain.tld/group1@domain.tld/calendar.pfb
+
+to just read the cached pfb, request
+
+https://servername/freebusy/user1@domain.tld/group1@domain.tld/calendar.pfb
+
 All pfb are readable for every (authenticated) user.
 The xpfb are only readable by users having read permissions 
 on the corresponding folders.
@@ -141,6 +149,13 @@
 given credentials of the users to try to access the xpfbs in the same way.
 If access to the xpfb is not possible, use the corresponding pfb.
 
+The URL for collected freebusy info is
+
+https://servername/freebusy/user1@domain.tld/group1@domain.tld.ifb
+
+and
+
+https://servername/freebusy/user1@domain.tld/group1@domain.tld.xfb
 
 Future
 ------





More information about the commits mailing list