Re: remote configuration sources
- From: Bob Smith <bob thestuff net>
- To: "Kenneth Lierman Jr." <kliermanm bigfoot com>
- Cc: Havoc Pennington <hp redhat com>, <gconf-list gnome org>
- Subject: Re: remote configuration sources
- Date: Mon, 20 Aug 2001 18:48:58 -0400 (EDT)
I'd like to add my $.02.
Before gconf was thaught up, a fiew programmers and myself went over the
concept of a configuration library and came up with an idea very similar to
gconf except that it was alot less complex on the server side. no schema's
or anything like that. just a registry style system with multiple
combinable backends. We decided that configureation data was not complex
enough to nessitate such things. User data on the other hand does.
bookmarks, addresses, and other such things are not configuration data so
they should be stored in a way better suited to them. LDAP already is
designed to do bookmarks, addressed and anything else you can think of.
We also looked at acap and we desided that it tries to duplicate LDAP.
Trying to use a 800LB garilla to pick flowers. I think the core gconf
people need to deside what constitutes configuration data and what
constitutes user data, and if both should be supported in gconf. If you
want both, my suggestion is to look over LDAP closly and see if it would
suit your needs (I think it would), find a server that would work (I dont
know any easy to install ones so one might need to be created) and go from
there.
On Mon, 20 Aug 2001, Kenneth Lierman Jr. wrote:
> >
> > I'm happy to help, you'll probably need to have pretty good ability to
> > dive into the GConf code and ACAP spec and figure out what's going on,
> > but feel free to ask questions as you do.
> >
>
> cool..... from my perspective (a heavy gnome user who wants some sort of
> remote configuration storage of adressbook, bookmarks, etc.), i guess i'd
> like an approach something like:
>
> 1) make sure acap and gconf can play long term
> 2) figure out a gconf schema/namespace/etc to store addressbook, bookmarks,
> etc
> 3) port some apps to use the new GConf stuff
> 4) add some sort of remote backend to GConf
> 4a) http or something rather simple
> 4b) acap or ????
>
> does this make sense? If so, i'd think getting to 4a would not take
> immense effort... 4b obviously could be a pretty big deal. Would probably
> depend on how much stuff could be reused from existing acapd's that exist.
>
> Ken
>
> _______________________________________________
> gconf-list mailing list
> gconf-list gnome org
> http://mail.gnome.org/mailman/listinfo/gconf-list
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]