Re: Single threading and CORBA_Object return types

[Dietmar Maurer <dietmar ximian com>]

Bill Haneman wrote:

> Dietmar Maurer wrote:
> >
> > Bill Haneman wrote:
> >
> > > Hi:
> > >
> > > I am trying to understand some behavior I am seeing and would like
> > > confirmation that it is a consequence of ORBit's single threading, and
> > > solicit suggestions for dealing with it.
> > >
> > > I am obtaining an instance of a registry object from OAF, and then
> > > need to query it (in a client).  It appears to me that if the client
> > > calls any functions that return CORBA_Object references, the return is
> > > accomplished via a push-IIOP stream from the server to the caller.
> > >
> > > This works fine if I make one such call; and I get the reply without
> > > entering the corba event loop (which I do via bonobo_main()).  However
> > > if I make two such calls in my client without entering bonobo_main the
> > > second call blocks in
> >
> > Why don't you enter the event loop with bonobo_main()? I suspect
> > everything will work fine then?
>
> ??
>
> What's the suggested tactic for making programmatic calls while inside
> bonobo_main() ?

Add an idle handler.

> The client is not an event-driven client, and of course bonobo_main()
> does not return.

or call bonobo_activate, like suggested by Michael.

- Dietmar