No background agent is needed to roll occurrences
of a recurring pattern in order for users to interact with those occurrences.
The calendar server makes any occurrence immediately usable for UI
interactions and resource availability interactions.
The following figure shows an example of a recurring
event created to start in 1920:Figure 1. Example of recurring event
starting in 1920
Immediately after a user creates this event,
that user or any other user can begin viewing and interacting with
occurrences of the event in 2011 or whenever. And if this event is
designed to make a resource busy, the system is immediately able to
calculate availability in 2011 or whenever.
The following figure shows a Calendar view of
the system derived occurrences in April 2011 for the recurring event
in the previous figure that started in 1920:Figure 2. Example of
recurring event calendar
