Dave Peticolas <[EMAIL PROTECTED]> writes:
> Oh my, yes. However, the mailing list archive on www.gnucash.org
> doesn't seem to have been updating itself lately. Maybe one of the
> main participants in that discussion could give a recap?
Here's the problem. We want gnucash to be able to schedule recurring
events, and we want external processes to be able to tell gnucash to
do things at particular times too. Both activites have to be
synchronized and have to be able to interact well with an already
running instance of gnucash that may or may not already have the file
open that the events are related to. All this makes things somewhat
complex.
I've realized that one fundamental question we have to answer is, "Do
we want to allow the user to have more than one copy of gnucash
running at the same time?" Until we decide that, it'll be hard to
decide what the right solution is, so I won't even bother outlining
the possibilities yet. Either answer implies fairly different
strategies.
One thing I'm sure of is that in order for gnucash to schedule events
that need to occur when it may not be running, it needs help from some
external daemon. You would think that that should just be at, and in
the short run, if we can figure out that at will run missed jobs
(because the system's down, or whatever), then that might be fine, but
in the longer run, I suspect we'll want/need to write our own daemon,
probably based on the at code, and not gnucash specific, that does
more (lets you get globally unique job ID's, remove jobs based on that
ID, specify whether or not missed jobs should be run, etc.)
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
