Re: [orbitcpp-list] Re: cpp branch: CORBA_Object struct hidden?
- From: murrayc t-online de (Murray Cumming)
- To: Michael Meeks <michael ximian com>
- Cc: Sam Couter <sam topic com au>, orbit-list <orbit-list gnome org>,orbitcpp-list <orbitcpp-list lists sourceforge net>
- Subject: Re: [orbitcpp-list] Re: cpp branch: CORBA_Object struct hidden?
- Date: 20 Feb 2002 10:45:26 +0100
On Wed, 2002-02-20 at 10:12, Michael Meeks wrote:
> On Tue, 2002-02-19 at 19:38, Murray Cumming wrote:
> > > > For instance, is there any kind of
> > > > instance ID? Can I create a 2nd CORBA_Object stub instance for the same
> > > > BonoboWindow?
> >
> > That wasn't a suggestion. It's a question from a CORBA newbie.
>
> Ahh ;-) ok.
>
> > Is it possible to get a 2nd stub for the same server instance? For
> > instance, can I have 2 BonoboWindow*s which can be used to manipulate
> > the same actual visible Bonobo window (forgive me if my capitalization
> > is wrong)?
>
> Ok; so BonoboWindow is not such a good example, since we can't get a
> CORBA reference to it; we can get a CORBA reference to a
> BonoboUIContainer [Bonobo_UIContainer] object.
>
> And yes we can get multiple references to it; simply doing
>
> new_ref = CORBA_Object_duplicate (old_ref, &ev);
That's exactly what I was looking for. I think it means that we don't
need to have a 1-to-1 mapping of C and C++ stub instances. So, we
shouldn't need that g_object_set_qdata()-like thing anymore. That should
have been obvious to me - this is CORBA, after all.
More thinking aloud, in case anybody cares or objects:
And I see no great advantage in inheriting from CORBA_Object, so I'll
look at making the CORBA_Object a member of CORBA::Object instead. That
conveniently solves the hidden CORBA_Object declaration issue too.
--
Murray Cumming
murrayc@usa.net
www.murrayc.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]