stuart: server/kolab/kolab/templates freebusy.conf.template, 1.7, 1.8

cvs at intevation.de cvs at intevation.de
Tue Sep 14 22:33:21 CEST 2004


Author: stuart

Update of /kolabrepository/server/kolab/kolab/templates
In directory doto:/tmp/cvs-serv13546/kolab/kolab/templates

Modified Files:
	freebusy.conf.template 
Log Message:
- Changed $extended to $params['extended'] which can be specified in freebusy.conf (i.e. can always generate xfb's if desired)
- Added $params['cache'] to control whether a cached result is returned, and whether the result of a vfb generation is cached for future use
- Both of the above can be controlled via URL parameters x and c, respectively (e.g. c=0 to turn off caching, c=1 to turn on caching). The URL parameters override the freebusy.conf settings.
- Added the ability to ignore specific events when generating the vfb. This is required for the resmgr script to properly handle event modification. Events can be specified by the url paramter i, and multiple events can be specified by doing e.g. i[]=one&i[]=two. The parameters to i should be urlencode()'ed UIDs of the specific events to ignore. If any events are to be ignored, caching is automatically turned off.
- Some small cleanups.


Index: freebusy.conf.template
===================================================================
RCS file: /kolabrepository/server/kolab/kolab/templates/freebusy.conf.template,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- freebusy.conf.template	31 Aug 2004 01:33:55 -0000	1.7
+++ freebusy.conf.template	14 Sep 2004 20:33:19 -0000	1.8
@@ -50,6 +50,14 @@
 // How many days of free/busy data should we generate?
 $params['freebusy_days'] = 56;
 
+// Should we generate extended free/busy information? This can be overridden by
+// the URL parameter "x" (= 0 or 1).
+$params['extended'] = false;
+
+// Should we use the caching mechanism, which avoids having to always re-read
+// all the events? This can be overridden by the URL parameter "c" (= 0 or 1).
+$params['cache'] = true;
+
 // Should we redirect using a Location header, if the user is not local? If this
 // is false we silently download the file ourselves and output it so that it
 // looks as though the free/busy information is coming from us.





More information about the commits mailing list