Re: Namespacing issues ...

[Michael Meeks <michael helixcode com>]

Hi Maciej,

On 18 Nov 2000, Maciej Stachowiak wrote:
> The ability to restart the daemon cleanly is clearly a required
> feature for GNOME 1.4, for this and other reasons; I just filed a
> bug on it.  (http://bugzilla.eazel.com/show_bug.cgi?id=4806).

        The ability to force a re-read of the configuration
information is rather vital, preferably without interrupting the
service to other users of oaf, this would be great to fix.

> In addition to OAF_INFO_PATH, the daemon reads a config file in /etc
> for it's path which can be modified cleanly by a provided program.
 
        I didn't realize that; this helps the situation considerably;
ISV's will just have to prepend their path to the beggining of this
file.

	It leaves component's users totaly at the mercy of the
packaging systems of various ISV's to determine which versions of
which components are installed, and where though.

> So I will also add monitoring of this file to oafd, so that it can
> reread it when it changes and reload the oafinfo files as
> appropriate.  (http://bugzilla.eazel.com/show_bug.cgi?id=4807)
        
        That sounds most useful.

> That means all you will have to do is call the program to tweak this
> config file in your rpm postinstall script and everything is peachy.

	Sounds good to me.

> Thanks for making sure this design issue gets addressed.

        Well, thank you ( and Elliot ) on behalf of all oaf users, for
a nice piece of software; my complaint is just that it could be still
better in the area of nice namespacing. We still have a separate,
uncontrolled namespace the 'oafinfo' namespace, which looks to me like
a very conflict prone area to me.

        Regards,

                Michael.

-- 
 mmeeks gnu org  <><, Pseudo Engineer, itinerant idiot