For a storage need in Thunderbird, a new application functionality,
we're evaluating which storage technology we should use, either SQLite
or IndexedDB.
My initial thought was to use SQLite.
Can we assume that SQLite APIs (resource://gre/modules/Sqlite.jsm) will
remain available for internal application code, including Thunderbird?
Are there strong reasons why either SQLite or IndexedDB should be preferred?
I see that IndexedDB doesn't guarantee that data will remain available,
rather the browser/platform may decide at any time to delete it when
storage is slow.
IndexedDB allows origin specific data, but our data isn't bound to an
origin, it's global application data.
Also it seems that IndexedDB gets mapped to raw sqlite storage? If true,
then IndexedDB could be seen as an unnecessary layer.
However, the argument has been brought up that in general, it could be
seen as a best practice for Thunderbird to prefer the use of
standardized web technologies, as it's less likely to get
deprecated/removed from the platform.
Thanks in advance for your thoughts,
Kai
--
You received this message because you are subscribed to the Google Groups
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/7e6fcbf7-f8d7-30fb-93de-0449f355d271%40kuix.de.
