Configuration Data Storage using GConf

1.0 References

[1] Software Architecture Document, Version 1.1 Revision 1.4, LiMo Foundation, 11 September 2007

2.0 Overview

LiMo Foundation Platform Release 1 uses GConf from the Gnome Project for configuration data storage and retrieval. GConf provides a simple configuration data storage interface to applications. Some of the features of GConf include:
  • Replaceable backend architecture: GConf currently has a single backend that stores configuration data in XML-format text files. However, the architecture allows a Registry-like binary database backend, an LDAP backend or even a full-blown SQL database backend.
  • Configuration key documentation: Applications can install documentation along with their configuration data, explaining the possible settings and the effect of each configuration key.
  • Data change notification service. All interested applications can be notified when configuration data changes. This means that applications built from components (where each component may be in a separate process) are much easier to write because if one component changes a setting the other components can discover the change and update themselves.
  • Abstract client API: Allows changes to the underlying implementation without requiring changes to applications.
  • Access locking: Protects configuration data from corruption when multiple applications try to access the data simultaneously.

3.0 Industry Standard

gconf-dbus 2.6.4.15 http://library.gnome.org/devel/gconf/2.20/

4.0 External API Documents

Additional GConf reference material can be found at: http://developer.gnome.org/feature/archive/gconf/gconf.html

5.0 Plug-in Extension Point Interface

None

6.0 Other Interfaces

None

7.0 Other Notes

None
Generated on Mon Mar 31 01:01:00 2008 by  doxygen 1.5.4