Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!csus.edu!ucdavis!csusac!sactoh0!unify!openlook!openlook-request
From: nannette@Eng.Sun.COM (Nannette Simpson)
Newsgroups: comp.windows.open-look
Subject: Re: calendar tool weirdness
Message-ID: <8cju99p@openlook.Unify.Com>
Date: 15 Apr 91 16:58:05 GMT
Lines: 25

The daemon, rpc.cmsd, stores only tokens to represent reminders.
It has no semantic knowledge of these tokens, nor does it execute
any action based on them.  It's up to the client (i.e. CM) to
ask for the next reminder token, interpret it in a manner appropriate
to its environment (i.e. CM is a window-based tool so putting
up a popup window is an appropriate interpretation of a token)
and execute it.

The problem is ... there is a certain class of reminders which
users expect to execute in the absence of any clients (i.e.
mail).  I refer to these as "persistent reminders."  Currently,
the tools make no distinction between client-specific and
persistent reminders.  That's why you must have a client (CM)
present for mail reminders to go off.

The design for reminders is being reworked.

______________________________________________________________________
Nannette Simpson			Internet: nannette@Eng.Sun.COM
Sun Microsystems, Inc.			UUCP: ...!sun!nannette
2550 Garcia Ave. MS 1-40		Phone: (415) 336-2969
Mountain View, CA 94043

Intelligence without character is a dangerous thing.
		--G. Steinem