New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use IndexDB to store data locally #13
Comments
See discussion in issue 1 of scalajs-rx-idb Here is a summary from the discussion: I think we agree that Rx and Actors are very different tools. So different in fact that one can build Rx on top of Actors :-)
So these two tools are very different, but can presumably be used together, either by building
That makes a very good case for backpressure. We may also want to have WebWorkers open connections to the web in read and write. ( I am not sure how well backpressure works over
This is where I am thinking Actors and Rx could work together (let's forget for the moment about what may or may not belong in the browser). What you have is a problem where a number of different parts of the code need to be aware of which transactions are happening: ie. they need to synchronise on these transactions. Since we don't and can't use Java like Also: In order to reduce lock starvation would it make sense to have a lot of little IndexDB databases? In my use case I am fetching Linked Data off the web, following links around the web. Would it make sense to have on DB per resource on the web? |
Would be very handy to increase startup time, and also to allow different components potentially running in different tabs but served by the same server to work easily together without needing to fetch all the data again each time. See issue #12: "component selection mechanism"
Requires one to write such a store, but it should be a lot easier in ScalaJS than in another language.
The text was updated successfully, but these errors were encountered: