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
We have a big problem with using localStorage for caching everything at the moment. When storing/syncing even just a couple of images, the storage limit is exceeded in most browsers and throws an exception, causing syncing to fail.
We either need a fundamental change in how remoteStorage.js caches data, or at least an exception with how it caches (or maybe not caches) binary data.
The first solution I could think of is IndexedDB. It has native support for storing blobs, and it doesn't have a global lock on every operation. Its size limit is much larger, and Firefox e.g. just asks for permission if you need more than 50MB.
As we need CORS anyway, almost all currently compatible browsers should also support IndexedDB.
It's really important, that we fix this very soon. It's basically impossible to use binary data in a real-world application at the moment. And even for other types of data, localStorage will not scale to what a lot of apps need. At least not if the default mode is to sync all data all the time.
The text was updated successfully, but these errors were encountered:
I have been wondering about this for some time now, but have yet to use
remoteStorage for anything substantial yet. I'm completely for moving to
IndexedDB too.
With the remoteStorage.js API, whether we use localStorage or IndexedDB (or
something new in the future), it will remain abstracted from the
application developers. This could be a huge plus for us in developer
adoption down the road. Just a thought.
We have a big problem with using localStorage for caching everything at the moment. When storing/syncing even just a couple of images, the storage limit is exceeded in most browsers and throws an exception, causing syncing to fail.
We either need a fundamental change in how remoteStorage.js caches data, or at least an exception with how it caches (or maybe not caches) binary data.
The first solution I could think of is IndexedDB. It has native support for storing blobs, and it doesn't have a global lock on every operation. Its size limit is much larger, and Firefox e.g. just asks for permission if you need more than 50MB.
As we need CORS anyway, almost all currently compatible browsers should also support IndexedDB.
It's really important, that we fix this very soon. It's basically impossible to use binary data in a real-world application at the moment. And even for other types of data, localStorage will not scale to what a lot of apps need. At least not if the default mode is to sync all data all the time.
The text was updated successfully, but these errors were encountered: