You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would be the best way to structure a machine focused solely on data-fetching / storage with IndexDb?
I have an api machine, which is responsible for communicating with the serve api. It has a variety of gql (or rest) queries that it can make, in response to a request event. It checks indexdb to see if it already has the data. If not, it fetches it and stores it, and then responds with the data.
The hope is that all this would take place in a web worker, so if I need to fetch some massive data-sets, its not using the main thread.
The text was updated successfully, but these errors were encountered:
What would be the best way to structure a machine focused solely on data-fetching / storage with IndexDb?
I have an api machine, which is responsible for communicating with the serve api. It has a variety of gql (or rest) queries that it can make, in response to a request event. It checks indexdb to see if it already has the data. If not, it fetches it and stores it, and then responds with the data.
The hope is that all this would take place in a web worker, so if I need to fetch some massive data-sets, its not using the main thread.
The text was updated successfully, but these errors were encountered: