Yes, that's the general idea, although we might optimize the init case if it turns out to be really popular.
On Oct 30, 2010, at 10:14, Henry Minsky <[email protected]> wrote: > > > On Sat, Oct 30, 2010 at 10:13 AM, Henry Minsky <[email protected]> wrote: > > > One idea would be to add a way to put the guard directly into the handler, > something like: > > <handler name="onisReady" reference="B" method="takeAction" when="inited" /> > > Roughly, this would extend the existing kernel mechanism that queues any > events send during <node>/construct and delivers them when construct is done. > We could create arbitrary queues for flags that acted as guards to delay > events. > > Comments? > > So the behavior you are proposing in the above example is > > when an onisReady event is sent from B: > > if A.isinited == true, run the handler > > I meant "If A.inited == true, run the handler", not "isinited" > > > if A.inited is false then that queues up the call to wait until the > "inited" attribute on A > is set to true, and then run? (using a new Delegate registered in > A.oninited?) > > > > -- > Henry Minsky > Software Architect > [email protected] > > > > > > -- > Henry Minsky > Software Architect > [email protected] > >
