Re: [Fresco-devel] problems with dead graphics again (sorry)

On Wed, Oct 29, 2003 at 08:46:52PM -0500, Stefan Seefeld wrote:
> in a potentially distributed environment like this, where every object 
> could be
> physically located on a different machine, every method invocation may 
> throw.
so... we have to be paranoid on every interface call *g*

> If it's a parent graphic that calls into a child graphic, the parent graphic
> will update its reference (i.e. set it to _nil) so the next time it doesn't
> even try to call.
ok

> On other occasions we have to be more careful so the scene graph doesn't get
> corrupted.
> The Traversal::update() call that is running into this is just updating
> a cache. As such, it should be totally transparent to the user. This means
> that if we can't update the cache, we must throw it out and start anew, but
> otherwise ignore the exception.
this means we don't do anything in TraversalImpl because the Traversal
corrupting just it's own stack of graphic-nodes?
we catch the exception in PositionalFocus and if it happens we delete the
Traversal and create a new? or we handle it inside TraversalImpl... 
cleaning the whole stack/cache... and try to fill it new from beginning?

> Stefan
thx for answer

cinap_lenrek