Resets and repops

[S001GMU at nova.wright.edu]

Date: Fri, 28 Mar 1997 11:01:23 -0800
From: claw at null.net

>-- The containment methods for the CT install watchers on everything
>that gets added to them. -- The watchers trigger on any state change
>to the watched object. -- Should the watched object leave the CT, the
>watcher deletes itself. -- The watchers monitor the sum weight of the
>objects, and report that to the CT on each state change for
>appropriate handling. -- Thus *any* action which directly affects an
>object in the CT will trigger a watcher, and result in the desired
>action. -- Problem: an object whose reported weight is dependant on
>the state of a remote object.  (eg the weight of the ballon is
>proportional to the total weight of a bucket in the castle.  Add rocks
>to the bucket in the castle, and the balloon gets heavier. This is not
>so easy to solve if the ballon is written to determine its weight only
>when its is queried.)

just put a watcher on the bucket and have it update the balloon's weight when
the bucket's weight changes, or send a signal to the balloon telling it it's
time to change it's weight.  It seems a bit silly to have a cause-effect chain
set up and then try to get info from the affected member without going thru
the chain (IE: set up the balloon to only calculate it's wieght when it's asked
to w/o having the bucket ask it to whenever the bucket's weight changes).

thus dropping a rock in the bucket would trigger the balloon to update it's
weight which would trigger the tree's watcher to recalculate everything and see
if Bubba falls out of the tree. Cause-effect, cause-effect.

would be pretty cool to watch from the castle.. 

*plunk*

...

*distant KAAARRASSSHH*  followed by "#$@%#$^$%^" from Bubba

-Greg