diff options
author | Ryan Lortie <desrt@desrt.ca> | 2011-09-11 12:44:36 -0400 |
---|---|---|
committer | Ryan Lortie <desrt@desrt.ca> | 2011-09-11 12:44:36 -0400 |
commit | 83e61fdbe0b71bc20c82789b56c48e6dcd44981a (patch) | |
tree | 1493eeb8cf53739d4ea657a52308d80776b62be9 /client | |
parent | 8f9f2b5ebd55164985c8330d33d0f8269da4a1c8 (diff) | |
download | dconf-83e61fdbe0b71bc20c82789b56c48e6dcd44981a.tar.gz |
Remove 'set lock' support from dconf
The dconf service can not presently be run at the system level and it
doesn't make sense to support locks on user-level databases. It also
became clear that most distributors and sysadmins would rather work
directly with text files anyway, so we supported that directly instead.
For this reason, 'set lock' support has never been properly implemented.
All the plumbing was added for it though, which means we have it
appearing on the API of the client library and documented in the help of
the commandline tool. This is misleading, since these functions do
nothing at all (and actually contain bugs anyway since their
do-nothingness was never actually tested).
For now, we rip out these functions. We can add them back later if we
decide to support this properly.
Diffstat (limited to 'client')
-rw-r--r-- | client/dconf-client.vala | 42 |
1 files changed, 0 insertions, 42 deletions
diff --git a/client/dconf-client.vala b/client/dconf-client.vala index 940abf2..8c011ae 100644 --- a/client/dconf-client.vala +++ b/client/dconf-client.vala @@ -204,48 +204,6 @@ namespace DConf { }*/ /** - * dconf_client_set_locked: - * @client: a #DConfClient - * @path: a dconf path - * @locked: %TRUE to lock, %FALSE to unlock - * @cancellable: a #GCancellable, or %NULL - * @error: a pointer to a #GError, or %NULL - * Returns: %TRUE if setting the lock was successful - * - * Marks a dconf path as being locked. - * - * Locks do not affect writes to this #DConfClient. You can still write to a key that is marked as - * being locked without problems. - * - * Locks are only effective when they are set on a database that is being used as the source of - * default/mandatory values. In that case, the lock will prevent writes from occuring to the database - * that has this database as its defaults. - **/ - public bool set_locked (string path, bool locked, Cancellable? cancellable = null) throws Error { - call_sync (engine.set_locked (path, locked), null, cancellable); - return true; - } - - /** - * dconf_client_set_locked_async: - * @client: a #DConfClient - * @path: a dconf path - * @locked: %TRUE to lock, %FALSE to unlock - * @cancellable: a #GCancellable, or %NULL - * @callback: the function to call when complete - * @user_data: the user data for @callback - * - * Marks a dconf path as being locked. - * - * This is the asynchronous version of dconf_client_set_locked(). You should call - * dconf_client_set_locked_finish() from @callback to collect the result. - **/ - public async bool set_locked_async (string key, bool locked, Cancellable? cancellable = null) throws Error { - yield call_async (engine.set_locked (key, locked), null, cancellable); - return true; - } - - /** * dconf_client_read: * @client: a #DConfClient * @key: a valid dconf key |