From 7672cda86c2632fef0284b5a62ba5fcaa5a32037 Mon Sep 17 00:00:00 2001 From: Federico Mena Quintero Date: Tue, 18 Jul 2000 17:19:25 +0000 Subject: Sync - Federico svn path=/trunk/; revision=4213 --- doc/devel/calendar/architecture.sgml | 48 +++++++++++++++++++++++++++++++++++- 1 file changed, 47 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/devel/calendar/architecture.sgml b/doc/devel/calendar/architecture.sgml index d4524fa857..08e4c82b35 100644 --- a/doc/devel/calendar/architecture.sgml +++ b/doc/devel/calendar/architecture.sgml @@ -8,8 +8,10 @@ that appear inside the Evolution shell. + + - Model/view separation + Model/View Separation Like other base components in Evolution, the calendar @@ -38,6 +40,50 @@ clients that are using the component's parent calendar. + + + + + Personal Calendar Server + + + The personal calendar server, or &PCS;, provides centralized + management and storage of a user's personal calendar. + Multiple clients can connect to the &PCS; simultaneously to + query and modify the user's calendar in a synchronized + fashion. The main features of the &PCS; are as follows: + + + + Storage + + + The &PCS; is responsible for loading and saving calendars. + Centralizing the loading and saving functionality allows + multiple clients to use the same calendar at the same time + without having to worry about each other. + + + + + Basic Queries + + + The &PCS; provides functions to do basic queries on a + calendar, for example, a client can ask the server for a + list of all the appointments in the calendar, or for all the + data for a specific appointment. + + + + + Recurrence and Alarm Queries + + + + + +