[Orbit-python-list] Re: How should O-P handle references to deactivated objects

[Christian R. R. <ki...@as...>]

(Back!)

On Sun, 27 May 2001, Jason Tackaberry wrote:

> > Say we deactivate an object through poa.deactivate_object(). If references
> > were generated to that object, what happens when we try and dereference
> > them?
>
> The correct behaviour would be for the ORB to raise
> CORBA.OBJECT_NOT_EXIST.

And could we add a custom handler that we could attach at runtime to get
the effect of manually loading objects in case they aren't there? This
would be cool to workaround dynamic loading (though our objects would have
to lose all state unless they persist).

If we want stateful on-demand loading (think client holds reference to
server; server dies, restarts; client uses reference) then the objects
have to be persisted.

> I know that OAF handles on-demand server loading.  I don't think there's
> any provision for this in ORBit itself, but I could be wrong.

The handler above could be placed in O-P. Is this a good idea, however?

Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311