This content has been marked as final. Show 2 replies
Right now we don't have a dedicated maintenance thread. The tasks are handled by the normal server threads. We use DB queues to schedule and execute operations like scheduling and notifications. Timestamps are set on entries to trigger purge/expiration of the entry at the right time.
Scheduling right now is done on a purely first come, first handled basis. For most part, the scheduling changes should be reflected in all parties' copies almost immediately.
For more information on Notification, see https://wikis.oracle.com/display/CommSuite/Using+Calendar+Server+7+Notifications .
There is a dedicated thread per queue, which only sleeps when there's nothing to do.
If anything changes in the queue, it is woken, so there should be no delays due to sleep
or lack of thread.