| commit | c15a1e3970e7c1567f6022bd85d9ab3267b08129 | |
| author | Ryan Lortie <desrt@desrt.ca> | |
| Wed, 9 Jan 2013 18:50:13 +0000 (9 13:50 -0500) | ||
| committer | Ryan Lortie <desrt@desrt.ca> | |
| Wed, 9 Jan 2013 20:29:37 +0000 (9 15:29 -0500) | ||
| tree | 0eab5df59bd17311a3de350fbb6a776ba3865291 | treesnapshot (tar.gz zip) |
| parent | 3f1b8d8bddbd35a801332e243f16b57c1eab815c | commitdiff |
engine: add a new database type: "service-db"
service-db databases are based on a gvdb in the user runtime dir
maintained by the dconf-service.
On startup, the client will send an Init message to the service to
ensure that the database is properly initialised. After that, things
are pretty much the same except that the values are read from the file
in the runtime dir instead of from the home directory.
We also drop the "shm" signalling mechanism for this case and instead
use the same invalidation trick that system databases use (ie:
overwriting the old gvdb header after writing the new file).
service-db databases are based on a gvdb in the user runtime dir
maintained by the dconf-service.
On startup, the client will send an Init message to the service to
ensure that the database is properly initialised. After that, things
are pretty much the same except that the values are read from the file
in the runtime dir instead of from the home directory.
We also drop the "shm" signalling mechanism for this case and instead
use the same invalidation trick that system databases use (ie:
overwriting the old gvdb header after writing the new file).