[sabayon] apply, start_monitoring, delegate construction and initial state
- From: John Dennis <jdennis redhat com>
- To: sabayon-list <sabayon-list gnome org>
- Subject: [sabayon] apply, start_monitoring, delegate construction and initial state
- Date: Tue, 22 Mar 2005 18:41:17 -0500
First a question:
When apply is called in a source/delegate module it is a separate
instance from when monitoring is invoked, right? This will be key in a
moment.
How does a delegate create it's initial state? In other words before
monitoring begins it might need to capture the state of the files its
going to monitor (so it can tell what's different in those files). When
can the delegate create this initial state? Delegates don't get called
for start_monitoring, which I think is the right moment. The delegate
constructor is not the right place, construction is not limited to
monitoring nor is it necessarily at the right moment. I considered
creating the initial state after being invoked to apply, thats not a bad
moment, except (see first question) I don't think the apply and the
monitoring are using the same objects, they're invoked indpendently
(right?)
So is the right answer that we need to add start_monitoring as a
delegate member and invoke it so delegates can initialize in preparation
for monitoring?
--
John Dennis <jdennis redhat com>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]