This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.
Each call to
SettingsManager.createLock() create a new
SettingsLock objects are kept in a queue of active locks. When a
SettingsLock object is created it's placed at the end of the queue. Calls to get/set places a request against the lock on which it's called. Requests run asynchronously and in the order they are placed against a lock. When the last request for a lock is run, and the success/error event against it has been fired, the lock is removed from the queue and the next lock start to be processed.
Indicates if the lock is no longer the active lock (
true) or if it's still the active lock (
Allows to change the values of a set of settings. This method is asychronous and return a
Allows to retrieve the value of a given setting. This method is asychronous and return a
Clears any action that have not been done yet (remember that
This method is added for testing and it deletes the whole settings DB!
Not part of any specification yet; however, this API will be discuss at W3C as part of the System Applications Working Group.