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
{{ message }}
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.
Hey there! ZboxFS looks like an awesome virtual file system, that has a lot of potential, however, I have noticed that there is no way to store and restore the created memory file system, rendering it totally volatile. It makes using Zbox is scenarios like WASM as an embedded file system nearly impossible without additional hacks.
Am I missing something there? Thanks! Great work so far!
The text was updated successfully, but these errors were encountered:
Thanks. Yes, the memory storage cannot be persisted because it is volatile. When the repo is closed, the memory storage is also released. So there is no way to open it again. To use in WASM, I think we need to wrap the memory storage in a static object, so that it can be re-used again.
Actually, that kind of reusable memory storage is already used in the faulty storage, which uses a in-memory static hashmap to store multiple memory storage. Take a look at it, hopefully that is what you want. In the future, I think we can extend current memory storage to include that feature. Thanks for your advice.
Hey there! ZboxFS looks like an awesome virtual file system, that has a lot of potential, however, I have noticed that there is no way to store and restore the created memory file system, rendering it totally volatile. It makes using Zbox is scenarios like WASM as an embedded file system nearly impossible without additional hacks.
Am I missing something there? Thanks! Great work so far!
The text was updated successfully, but these errors were encountered: