Re: Exposing gconf key names

[Malcolm Tredinnick <malcolm commsecure com au>]

On Sun, May 18, 2003 at 01:24:58PM +0200, Christophe Fergeau wrote:
> > How would this work? It sounds like gconf_client_get_value(). Or are
> > you suggesting that it would try to use CONF_HTTP_PROXY_HOST and, if
> > that is not defined, use OLD_CONF_PROXY_HOST or something?
> 
> At first this would indeed only do a gconf_client_get_value, but app
> writer not wanting to deal with gconf wouldn't have to. And abstracting
> this stuff a bit would let us change gconf keys, or do some other stuff
> at a later time without breaking apps using it (for example, iirc gconf
> isn't thread safe, which potentially causes problems when getting the
> proxy settings from the http method, fixing that may be hidden in a
> gnome_vfs_get_proxy_host or something).

Thinking about this some more, I am becoming less worried by backwards
compatibility issue. The thing is that good gconf behaviour requires an
application which owns a gconf key to place nicely w.r.t backwards
compat anyway (this is written in one of Havoc's documents, but I canot
find it right at the moment). So if, in the example here, gnome-vfs
changes the name of a key, it should define a _new_ constant for that
key, not change an old one.

Malcolm

-- 
No one is listening until you make a mistake.