From a79e75db7cd48339ec3c09f37bd0d7453d111a5d Mon Sep 17 00:00:00 2001 From: Philip Withnall Date: Wed, 11 Aug 2021 09:54:44 +0100 Subject: docs: Add README Add a simple readme containing a brief braindump of how GVDB works and its strengths and weaknesses. Signed-off-by: Philip Withnall --- README.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..2c53d77 --- /dev/null +++ b/README.md @@ -0,0 +1,25 @@ +GVDB +==== + +GVDB (GVariant Database) is a simple database file format that stores a +mapping from strings to GVariant values in a way that is extremely +efficient for lookups. + +The code is intended to be pulled into projects as a submodule/subproject, +and it is not shipped as a separately compiled library. It has no API +guarantees. + +A GVDB database table is a single file. It is designed to be memory mapped +by one or more clients, with accesses to the stored data being fast. The +storage format has low size overheads, assuming the GVariant formats for +values do not require much padding or alignment. + +Modifying a GVDB table requires writing out the whole file. This is +relatively slow. `gvdb_table_write_contents()` does this by writing out +the new file and atomically renaming it over the old one. This means +that any clients who have memory mapped the old file will need to reload +their memory mapping. + +This means that if multiple clients are using a GVDB table, an external +process is needed to synchronise writes and to notify clients to reload +the table. `dconf-service` is an example of such a process. -- cgit v1.2.1