1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237
|
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
#include "nsISupports.idl"
#include "nsIVariant.idl"
interface nsIKeyValueDatabaseCallback;
interface nsIKeyValueEnumeratorCallback;
interface nsIKeyValuePairCallback;
interface nsIKeyValueVariantCallback;
interface nsIKeyValueVoidCallback;
interface nsIKeyValuePair;
/**
* The nsIKeyValue* interfaces provide a simple, asynchronous API to a key/value
* storage engine. Basic put/get/has/delete operations are supported, as is
* enumeration of key/value pairs and the use of multiple named databases within
* a single storage file. Operations have ACID semantics.
*
* This API does not (yet) support transactions, so it will not be appropriate
* for all use cases. Extension of this API to support transactions is tracked
* by bug 1499238.
*
* The kvstore.sys.mjs module wraps this API in a more idiomatic, Promise-based
* JS API that supports async/await. In most cases, you're better off using
* that API from JS rather than using this one directly. Bug 1512319 tracks
* native support for Promise in Rust-implemented XPCOM methods.
*/
/**
* The key/value service. Enables retrieval of handles to key/value databases.
*/
[scriptable, builtinclass, rust_sync, uuid(46c893dd-4c14-4de0-b33d-a1be18c6d062)]
interface nsIKeyValueService : nsISupports {
cenum RecoveryStrategy: 8 {
ERROR,
DISCARD,
RENAME,
};
/**
* Get a handle to an existing database or a newly-created one
* at the specified path and with the given name.
*
* The service supports multiple named databases at the same path
* (i.e. within the same storage file), so you can call this method
* multiple times with the same path and different names to retrieve
* multiple databases stored in the same location on disk.
*/
void getOrCreate(
in nsIKeyValueDatabaseCallback callback,
in AUTF8String path,
in AUTF8String name);
void getOrCreateWithOptions(
in nsIKeyValueDatabaseCallback callback,
in AUTF8String path,
in AUTF8String name,
[optional] in nsIKeyValueService_RecoveryStrategy recoveryStrategy);
};
/**
* A key/value database.
*
* All methods are asynchronous and take a callback as their first argument.
* The types of the callbacks vary, but they can all be implemented in JS
* via an object literal with the relevant methods.
*/
[scriptable, builtinclass, rust_sync, uuid(c449398e-174c-425b-8195-da6aa0ccd9a5)]
interface nsIKeyValueDatabase : nsISupports {
/**
* Write the specified key/value pair to the database.
*/
void put(
in nsIKeyValueVoidCallback callback,
in AUTF8String key,
in nsIVariant value);
/**
* Write multiple key/value pairs to the database.
*
* It supports two types of write:
* * Put a key/value pair into the database. It takes a nsIKeyValuePair
* where its key and value follow the same types as the put() method.
* * Delete a key/value pair from database. It takes a nsIkeyValuePair
* where its value property must be null or undefined.
*
* This features the "all-or-nothing" semantics, i.e. if any error occurs
* during the call, it will rollback the previous writes and terminate the
* call. In addition, writeMany should be more efficient than calling "put"
* or "delete" for every single key/value pair since it does all the writes
* in a single transaction.
*
* Note:
* * If there are multiple values with the same key in the specified
* pairs, only the last value will be stored in the database.
* * Deleting a key that is not in the database will be silently ignored.
* * If the same key gets put and deleted for multiple times, the final
* state of that key is subject to the ordering of the put(s) and delete(s).
*/
void writeMany(
in nsIKeyValueVoidCallback callback,
in Array<nsIKeyValuePair> pairs);
/**
* Retrieve the value of the specified key from the database.
*
* If the key/value pair doesn't exist in the database, and you specify
* a default value, then the default value will be returned. Otherwise,
* the callback's resolve() method will be called with a variant
* of type VTYPE_EMPTY, which translates to the JS `null` value.
*/
void get(
in nsIKeyValueVariantCallback callback,
in AUTF8String key,
[optional] in nsIVariant defaultValue);
/**
* Determine whether or not the key exists in the database.
*/
void has(
in nsIKeyValueVariantCallback callback,
in AUTF8String key);
/**
* Remove the key/value pair with the given key from the database.
*
* If the given key doesn't exist in the database, this operation doesn't
* fail; or rather, it fails silently, calling the resolve() method
* of its callback rather than reject(). If you want to know whether
* or not a key exists when deleting it, call the has() method first.
*/
void delete(
in nsIKeyValueVoidCallback callback,
in AUTF8String key);
/**
* Clear all the key/value pairs from the database.
*/
void clear(in nsIKeyValueVoidCallback callback);
/**
* Enumerate key/value pairs, starting with the first key equal to
* or greater than the "from" key (inclusive) and ending with the last key
* less than the "to" key (exclusive) sorted lexicographically.
*
* If either key is omitted, the range extends to the first and/or last key
* in the database.
*/
void enumerate(
in nsIKeyValueEnumeratorCallback callback,
[optional] in AUTF8String fromKey,
[optional] in AUTF8String toKey);
};
/**
* A key/value pair. Returned by nsIKeyValueEnumerator.getNext().
*/
[scriptable, uuid(bc37b06a-23b5-4b32-8281-4b8479601c7e)]
interface nsIKeyValuePair : nsISupports {
readonly attribute AUTF8String key;
readonly attribute nsIVariant value;
};
/**
* An enumerator of key/value pairs. Although its methods are similar
* to those of nsISimpleEnumerator, this interface's getNext() method returns
* an nsIKeyValuePair rather than an nsISupports, so consumers don't need
* to QI it to that interface; but this interface doesn't implement the JS
* iteration protocol (because the Rust-XPCOM bindings don't yet support it),
* which is another reason why you should use the kvstore.sys.mjs module from JS
* instead of accessing this API directly.
*/
[scriptable, builtinclass, rust_sync, uuid(b9ba7116-b7ff-4717-9a28-a08e6879b199)]
interface nsIKeyValueEnumerator : nsISupports {
boolean hasMoreElements();
nsIKeyValuePair getNext();
};
/**
* A callback for the nsIKeyValueService.getOrCreate() method.
*
* The result is an nsIKeyValueDatabase.
*/
[scriptable, uuid(2becc1f8-2d80-4b63-92a8-24ee8f79ee45)]
interface nsIKeyValueDatabaseCallback : nsISupports {
void resolve(in nsIKeyValueDatabase database);
void reject(in AUTF8String message);
};
/**
* A callback for the nsIKeyValueDatabase.enumerate() method.
*
* The result is an nsIKeyValueEnumerator.
*/
[scriptable, uuid(b7ea2183-880b-4424-ab24-5aa1555b775d)]
interface nsIKeyValueEnumeratorCallback : nsISupports {
void resolve(in nsIKeyValueEnumerator enumerator);
void reject(in AUTF8String message);
};
/**
* A callback for the nsIKeyValueEnumerator.getNext() method.
*
* The result is the next key/value pair, expressed as separate key and value
* parameters.
*/
[scriptable, uuid(50f65485-ec1e-4307-812b-b8a15e1f382e)]
interface nsIKeyValuePairCallback : nsISupports {
void resolve(in nsIKeyValuePair pair);
void reject(in AUTF8String message);
};
/**
* A callback for the nsIKeyValueDatabase.has() and .get() methods.
*
* The result is an nsIVariant, which is always a boolean for the has() method
* and can be any supported data type for the get() method.
*/
[scriptable, uuid(174ebfa1-74ea-42a7-aa90-85bbaf1da4bf)]
interface nsIKeyValueVariantCallback : nsISupports {
void resolve(in nsIVariant result);
void reject(in AUTF8String message);
};
/**
* A callback for the nsIKeyValueDatabase.put() and .delete() methods.
*
* There is no result, but the resolve() method is still called when those
* async operations complete, to notify consumers of completion.
*/
[scriptable, uuid(0c17497a-ccf8-451a-838d-9dfa7f846379)]
interface nsIKeyValueVoidCallback : nsISupports {
void resolve();
void reject(in AUTF8String message);
};
|