bernhard: doc/architecture freebusy.txt,1.8,1.9

[cvs at intevation.de]

Author: bernhard

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

Modified Files:
	freebusy.txt 
Log Message:
Tried to update freebusy trigger information, 
as this basically decided and working.
Added principal authors of this freebusy concept with partical freebusy lists.


Index: freebusy.txt
===================================================================
RCS file: /kolabrepository/doc/architecture/freebusy.txt,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- freebusy.txt	21 Oct 2004 05:49:54 -0000	1.8
+++ freebusy.txt	27 Jan 2005 15:43:38 -0000	1.9
@@ -1,5 +1,6 @@
 How to handle freebusy lists for Kolab2
 Draft
+Principal authors: Martin Konold, Bernhard Reiter
 $Id$
 
 Notations
@@ -134,25 +135,31 @@
 
 On the server we use mod_rewrite to parse URLs like.
 
-https://servername/freebusy/trigger/user1@domain.tld/user1@domain.tld/calendar.pfb
-https://servername/freebusy/trigger/user1@domain.tld/group1@domain.tld/calendar.pfb
-
-The final syntax for these URLs has to be decided upon.
+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 
 the server side code. The server side code then uses these credentials to 
 access the calendar folders and to write the pfbs.
 
-To trigger creation of a pbf, issue a HTTP GET request to
+To trigger creation of a pbf (and xpdf), issue a HTTP GET request like:
 
-https://servername/freebusy/trigger/user1@domain.tld/group1@domain.tld/calendar.pfb
+	https://servername/freebusy/trigger/X/PATH/FOLDERNAME.pfb
+	
+	with X being one of
+		a) the "name" part before the @ of the primary email address.
+		   Clients triggering for folders of other users can derive
+		   this from the corresponding imap path component.
+		b) the uid
 
-All pfbs are readable for every (authenticated) user though normal users don't require 
-to read the pfbs but the pfb collector must be able to 
-read all pfbs from potentially many servers (multi-location setups).
+All pfbs are readable for every (authenticated) user 
+though normal users don't require to read the pfbs 
+but the pfb collector must be able 
+to read all pfbs from potentially many servers (multi-location setups).
 
 The xpfb are only readable by users having read permissions 
-on the corresponding folders. Creation of xpfbs happens at when pfbs are created.
+on the corresponding folders. 
+Creation of xpfbs happens at when pfbs are created.
 
 In general all clients writing to calendar folders including the KDE Client Kontact, the Outlook Clients,
 the web client and the resource scripts must trigger the generation of pfbs.
@@ -172,13 +179,10 @@
 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
+The URLs for collecting freebusy info are
 
-https://servername/freebusy/user1@domain.tld/group1@domain.tld.xfb
+https://servername/freebusy/group1@domain.tld.ifb
+https://servername/freebusy/user1@domain.tld.xfb
 
 Future
 ------