-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
WasmFS: OPFS AccessHandles backend #15950
Comments
This was started in #16813. The backend creates an exclusive AccessHandle for each opened file, so each file can only be opened once at a time. Improving that is tracked in #17121. We also need to make the error handling in the opfs backend more robust with tests for the different things that could go wrong. |
The error handling issue has been fixed and the OPFS backend is generally usable now. |
Is there any documentation on this? I've looked in the emscripten docs but I can't find any info about it (https://emscripten.org/docs/api_reference/Filesystem-API.html#file-system-api). I'd love to use it for my custom PNG encoder wasm implementation. |
@rulkens coincidence, i am also looking for it for a better data persistence process. I found that there is a good example c source code, which can be used as a documentation at https://github.com/emscripten-core/emscripten/blob/main/test/wasmfs/wasmfs_opfs.c |
We should write a new WasmFS backend using OPFS AccessHandles to provide efficient access to the native file system.
Depends on #15946.
The text was updated successfully, but these errors were encountered: