Labs/Jetpack/JEP/11: Difference between revisions

Jump to navigation Jump to search
m
mNo edit summary
Line 27: Line 27:
Persistent storage will live at <code>jetpack.storage.simple</code>. The <code>jetpack.storage</code> namespace will provide access to any other available storage systems, such as SQLite, secure/password storage, and so on.  The current <code>jetpack.sessionStorage</code> object, which allows arbitrary JS objects (they need not be JSON-able) to be stored between reloads of a Jetpack within the same Firefox session, will be renamed to <code>jetpack.storage.session</code>.
Persistent storage will live at <code>jetpack.storage.simple</code>. The <code>jetpack.storage</code> namespace will provide access to any other available storage systems, such as SQLite, secure/password storage, and so on.  The current <code>jetpack.sessionStorage</code> object, which allows arbitrary JS objects (they need not be JSON-able) to be stored between reloads of a Jetpack within the same Firefox session, will be renamed to <code>jetpack.storage.session</code>.


==== Callbacks ====
==== Asynchronicity and Callbacks ====


Because of the asynchronous nature of this API, its operations communicate their statuses and results to callers via callbacks.  In the context of simple storage, a callback is either a function or an object that defines the methods <code>onResult</code> and <code>onError</code>.  If a callback is a function, it is called when its associated asynchronous operation successfully completes.  If a callback is an object, its <code>onResult</code> method (if defined) is called when the operation successfully completes, and its <code>onError</code> method (if defined) is called when an error occurs during the operation.  This allows callers to provide a simple function in the common case; only if callers wish to be notified of errors do they need to use the more verbose object form.
Because of the asynchronous nature of this API, its operations communicate their statuses and results to callers via callbacks.  In the context of simple storage, a callback is either a function or an object that defines the methods <code>onResult</code> and <code>onError</code>.  If a callback is a function, it is called when its associated asynchronous operation successfully completes.  If a callback is an object, its <code>onResult</code> method (if defined) is called when the operation successfully completes, and its <code>onError</code> method (if defined) is called when an error occurs during the operation.  This allows callers to provide a simple function in the common case; only if callers wish to be notified of errors do they need to use the more verbose object form.
Confirmed users
764

edits

Navigation menu