Re: Corba-izing gnome-pilot

["deity dbc dk" <deity trinity dbc bib dk>]

On Fri, 20 Nov 1998, Manish Vachharajani wrote:

> > CORBA_ORB to conduit_get_gpilot_conduit.  Each conduit should not
> > create it's own orb, but use the pilot's.  In addition, gpilotd should
> I am not too familiar with how ORBit works, but if we don't pass this
> parameter, will the conduit just create its own data structures to

A CORBA_ORB structure is the structure used to all orb interaction,
included is requesting a object of type blah.

Giving the CORBA_ORB to the conduit will spare the extra memory and
overhead of an extra CORBA_ORB structure, it may, however, never share the
exception structure.

I think giving the orb to the conduit it ok. In the orb part, I currently
have the CORBA_ORB as a global variable. If i move it into
GPilotd_Orb_Context, manager.cc can access the ORB_Context and get the
CORBA_ORB. We can then pass it along in GPilotDBInfo, with the
pilot_socket etc. Does that sound reasonable ?

Ad. regstrating the gpilotd. Currently I put the IOR in
.gnome/CORBA-servers like the panel does, is this the registration you
mean, or do you mean something from libgnorba ? (goad_server_register
looks like a prospect).

I won't use gnome_CORBA_init since it also initializes gtk+.

eskil
---