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

[Jason T. <ta...@li...>]

> 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).

CORBA has a provision for a POA to have a default servant, which handles
requests for unknown objects.  This could potentially be used for
something like this, but it's probably not the best solution.  ORBit
even supports this, but O-P doesn't yet.

> 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.

This stuff happens at a level below ORBit-Python.  If it can be done,
ORBit has to support it.

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

Well, if OAF does it, and there are OAF bindings, I don't see any big
benefit.

Jason.