Confirmed users
483
edits
No edit summary |
No edit summary |
||
Line 67: | Line 67: | ||
Whichever solution we find for this, it should work in all browsers. If we end up creating a JS library, we need to be sure that it works (or will work, thinking about [http://caniuse.com/#search=indexeddb IndexedDB support]) in all the major browsers. We believe that we can avoid adding a new web API for this, but in case that we finally need to do it, it would be great if we could standardize it and avoid repeating the DataStore fiasco. | Whichever solution we find for this, it should work in all browsers. If we end up creating a JS library, we need to be sure that it works (or will work, thinking about [http://caniuse.com/#search=indexeddb IndexedDB support]) in all the major browsers. We believe that we can avoid adding a new web API for this, but in case that we finally need to do it, it would be great if we could standardize it and avoid repeating the DataStore fiasco. | ||
==== Javascript library ==== | ==== Javascript library ==== | ||
This is still under discussion, but the current proposal is to create a JS library that exposes a [http://pouchdb.com/ PouchDB] inspired API but also gives a direct access to the underlying data source API by exposing a [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy proxified] instance of the used data source (initially limited to IndexedDB). This way the developers should be able to use the new improved API or keep using the specific data source API. This library should handle all the synchronization of data with the Firefox Cloud server, the resolution of conflicts, the migration from a currently existing database, the authentication part and the remote storage auth management, the encryption and decryption of the data in the client... | |||
===== API ===== | ===== API ===== | ||
== Current status == | == Current status == | ||
=== Service === | === Service === | ||
=== Client === | === Client === |