The rrules parameter takes a semicolon-separated list of quoted recurrence rule strings. Each string represents a recurrence rule of the event. Each string must be enclosed in quotes. Many parameters are possible for recurrence rules. (See RFC 2445 for a complete description of the syntax.)
Three parameters used by Calendar Server for specifying recurrence are freq, count and until:
The freq parameter in a rule defines the periodicity of the event, and has the following possible values:
DAILY |
The event recurs daily. |
WEEKLY |
The event recurs weekly. |
MONTHLY |
The event recurs monthly. |
YEARLY |
The event recurs yearly. |
The count parameter in a rule defines how many times the meeting repeats. If you do not specify the count, the default is the maximum number of recurrences allowed. The default maximum is 60. To change the maximum number, set the server configuration preference calstore.recurrence.bound.
The until parameter in a rule specifies using an end date as opposed to using the count to limit the number of instances created. Instances are created up to the end date or until 60 instances are created, whichever occurs first.
In the event that neither the count nor the until parameter are specified, the default is 60 instances.
Using the storeevents.wcap command to create an event with only exdates or rdates values, without specifying an rrules results in no events being created. The same behavior can be observed with the storetodos.wcap command.
The following example shows an rrules parameter that specifies the event is to occur daily for 10 instances (COUNT=10;FREQ=DAILY):
rrules="count%3D10%3Bfreq%3Ddaily" |
The following example URL passes the example rrules parameter:
http://webcalendarserver/storecomponents.wcap ?id=b5q2o8ve2rk02nv9t6 &calid=jdoe &uid=333 &dtstart=20020301T112233Z &rrules="count%3D10%3Bfreq%3Ddaily" &dtend=20020301T112233 &summary=uuuu |