-
-
Notifications
You must be signed in to change notification settings - Fork 151
Data Model
David Scrobonia edited this page Jun 27, 2018
·
3 revisions
All tool data should be stored in memory in the tool's module closure. Because we are using a heartbeat to keep the service worker activated at all time the idea is it won't terminate and the in memory data should be fine. (see the service worker lifecycle for more context) In addition to keeping the data in memory, we also want to write the data to indexeddb
, the asynchronous data store built into browsers. Writing the all of the data to indexeddb
is so that we can persist data between HUD Sessions and to load data into the various HUD iframes (panels and bottom drawer) when the target page is reloaded.
Below is a rough (and overly complex) diagram of the data model.