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
Copy file name to clipboardExpand all lines: README.md
+15-10Lines changed: 15 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,13 +27,12 @@ Here's a closer look at the Phoenix VFS organization:
27
27
28
28
-**Node Websocket Connector Integration**:
29
29
- The `/tauri/` paths can be accessed via websockets. This integration is much more
30
-
performant than tauri's fs rust APIs(generally 4x faster and 10x faster for large files).
30
+
performant than Tauri's fs rust APIs(generally 4x faster and 10x faster for large files).
31
31
- As we use websockets to connection to a node process that executes the actual fs operations,
32
32
the ws backed `/tauri/` apis are available in all web/shared/service workers.
33
-
- This is recommended to use in main browser window as well, as this will releive the main thread
33
+
- This is recommended to use in main browser window as well, as this will relieve the main thread
34
34
of tauri fs access apis that typically leads to blocking/freezing js window on large file access.
35
-
- Supports filesystem watcher APIs. On all other endpoints, the virtual watchers are only capable of
36
-
emitting file change events on files that has been modified within its window/browser only.
35
+
- Supports filesystem watcher APIs that behaves consistently across all platforms.
37
36
38
37
By adopting Phoenix VFS, you're not just leveraging a file system; you're integrating a dynamic, adaptable layer that bridges the web and native worlds, making your web applications more powerful and reduces development time and costs.
39
38
@@ -54,6 +53,7 @@ By adopting Phoenix VFS, you're not just leveraging a file system; you're integr
0 commit comments