<br><font size=2><tt><b>Havoc Pennington <hp@redhat.com></b> wrote
on 04/07/2005 10:18:23 AM:<br>
> Previously I have posted:<br>
> http://www.gnome.org/projects/gconf/plans.html<br>
> which are some changes to make to gconf, with three of those changes<br>
> prioritized as more important vs. the others.<br>
> </tt></font>
<br>
<br><font size=2><tt>In these plans the client library is both a thin convenience
layer over the D-BUS interface and responsible for loading/enforcing the
schemas. If I have this right, there are two client layers: raw configuration
DBUS service, and validated configuration from a schema library. Should
these two layers be considered in separate specs?</tt></font>
<br><font size=2><tt><br>
My interest in a configuration system is to provide desktop integration
for Java applications. The desires are:</tt></font>
<br><font size=2><tt>- Minimal amount of shared libraries in the client
process.</tt></font>
<br><font size=2><tt>- Single api for all ui desktops.</tt></font>
<br>
<br><font size=2><tt>chas</tt></font>