Wrapping a libbonobo object as a CORBA object

[ERDI Gergo <cactus cactus rulez org>]

Hi,

I'd like Bonobomm to support the easy creation of implementations for new
interfaces, by allowing you to re-use the existing Bonobo implementations
from libbonobo. This means our Bonobomm classes will have to be a
descendent of the relevant ORB skeleton classes.

This has several implications, one of them is that it will have two CORBA
objects, and forward between them:
	1. User creates a new BOnobomm object
	2. bonobomm object creates a libbonobo object
	3. libbonobo object creates an ORBit CORBA object
	4. bonobomm object creates a new CORBA object (thru the
constructor inherited from the skeleton class)

This means all CORBA calls will be forwarded by the bonobomm wrapper to
the libbonobo object (by the usual Gtkmm WRAP_METHOD method). Does it
have any side-effect to have two CORBA objects that are in some way the
same? Also, does it have any overhead to call a CORBA method on a local
object over a normal function call?

[ the rest is only meant for the bonobomm list ]

The other side-effect of the bonobomm objects being CORBA objects
themselves is that the current (default?) ORBit/C++ IDL compiler creates
code that uses C concepts like char* for string and funny structs instead
of vector<>s. Is there a really native C++ ORBit IDL compiler frontend?

-- 
   .--= ULLA! =----------------------------.  finger cactus cactus rulez org
   \      http://cactus.rulez.org           \   for PGP public key
    `----------= cactus cactus rulez org =--'
Rosszak a reflexeim. Egyszer elutott egy auto, amit 2 ember tolt.