[omniORB] Callback loop stalling: sample code

[Kevin Bailey]

On Thu, Nov 02, 2000 at 05:11:46PM +0000, Duncan Grisby wrote:
> 
> ...

Thanks for the detailed explanation!

> There are a few things we could do in omniORB to help with this
> situation, and we might think about it for future versions. In the
> mean-time, a work-around is for B to keep a reference to an object in
> A's address space -- for example the first callback object received.
> That prevents the closure of the connection, so all calls are
> dispatched on the same thread.

Ya, I guess I'll cache the last few references within B but a
better implementation would probably cache the last second's
worth of references.