avi at alkalay.net
Tue Apr 27 23:45:50 EEST 2004
What I mean was: Should this API/library be designed to be used also by
non-desktop software (Apache, Samba, mount, pure glibc, modprobe, etc that
WANTS to use it), or only for desktop apps?
If the first is true, the design must think about dependencies and
----- Original Message -----
From: "Sean Middleditch" <elanthis at awesomeplay.com>
To: <xdg at freedesktop.org>
Sent: Tuesday, April 27, 2004 3:49 PM
Subject: Re: Configuration API
> On Tue, 2004-04-27 at 14:10, Avi Alkalay wrote:
> > I agree something must be defined.
> > Do you guys think it is important for this API to be desktop-apps-only
> > or also systemwide?
> > Like, should XFree, Apache configuration be accessible through this API
> If they want to be. It's up to them. You can't shove configuration
> systems/APIs down peoples' throats. The X11 server (XFree86 or
> otherwise) is something that should be configurable on the fly IMO given
> that it *is* a desktop component, though. ;-)
> Do server projects impose any additional needs on a configuration API?
> An administrator running a server farm might *love* to have Apache for
> example share its settings with other servers on the network and all
> support change notification to provide for simplified central
> administration. (Admin opens tool on his desktop, changes a setting
> that gets distributed across the network using a cluster-oriented
> backend, apache processes pick up the change and adjust accordingly.)
> They would perhaps require atomicity for change sets (you don't want to
> open temporary an access/security hole because some changes that should
> have been made all at once are picked up and immediately handled one by
> > Regards,
> > Avi
> Sean Middleditch <elanthis at awesomeplay.com>
> AwesomePlay Productions, Inc.
> xdg mailing list
> xdg at freedesktop.org
More information about the xdg