https://bugs.kde.org/show_bug.cgi?id=330192
--- Comment #14 from Nate Graham <pointedst...@zoho.com> --- Thanks for engaging with me on this, David. Much appreciated. As far as I know, GNOME users are expected to first mount the remote location using Nautilus, yes. It's also possible that the mounts can automount in response to filesystem events that request a path that was previously on one of the FUSE mounts. That's just speculation though (but it sounds cool and useful, and I know that macOS does this). Essentially the key difference is that GIO provides a FUSE mount for non-GNOME apps, which allows all POSIX-compatible apps to access network locations normally. KIO provides this support without a FUSE mount and instead just downloads the remote files locally to a temp location and then re-uploads them after the app quits, which is associated with the drawbacks mentioned in this bug and all the duplicates. I'm not advocating that we use FUSE for everything, but rather proposing that we do the same thing as GIO and make a "KVFs" that provides similarly transparent access to non-KIO-aware POSIX apps so our users don't have to choose non-KDE apps that have Samba clients or understand the implementation details of how files get read, stored, and saved back to the remote location. -- You are receiving this mail because: You are watching all bug changes.
