https://bugs.kde.org/show_bug.cgi?id=75324
--- Comment #93 from Konstantin Kharlamov <hi-an...@yandex.ru> --- (In reply to Christoph Feck from comment #92) > > First pre-requisite step is making all KDE apps robust to blocking calls on > > files which it thinks are safe as they're on the local file system. > > Uh, no. KDE applications are expected to use KIO. You would have to fix all > _other_ applications, which don't use the KIO API. I guess applications > using GIO are also safe, because (I hope) GIO was also designed > asynchronous. But POSIX API is synchronous, and users of those applications > just have to live with UI hangs unless they use separate threads for IO. It's okay to use KIO, nobody advises to drop it. Idea is just to improve a usability on FUSE mounts a little bit. You can't reasonably expect every existing app out there to implement a new protocol just to make it compatible with KDE. Also, imagine how bloated servers would become if every terminal utility would implement KIO just because on KDE-powered desktops it's the way to go. --------- The main selling point of FUSE is that nobody have to implement anything, it just works™. -- You are receiving this mail because: You are watching all bug changes.
