Re: GConf and bonobo-conf

[Havoc Pennington <hp redhat com>]

Dietmar Maurer <dietmar ximian com> writes:
> Havoc Pennington wrote:
> 
> > Some issues to consider when proposing a solution:
> >
> >  - notification of changed values has to be fast, and it sends
> >    the contents of the value over the wire. Thus,
> >    GConf values really can't be large.
> 
> Another reason to use CORBA_any instead of ConfigValue.
> 

If we just want CORBA_any for that, it can be used as a private
implementation detail in GConf.idl. ConfigValue is not publically
exposed, it's a nasty-ass private IPC hack as is all of GConf.idl.

There was a reason CORBA_any isn't used in GConf.idl, which I don't
remember. I think it may have been broken/unimplemented in ORBit at
the time, or something. I don't remember. 

But both CORBA_any and ConfigValue have unbounded size, and the size
of them containing an int is no big deal. The problem is if you put a
big data structure or big string in there. And that problem exists 
for both. 

Anyway, any argument involving GConf.idl is about gconf implementation
details, not the public API.

Havoc