Warning, /frameworks/kio/src/kioexec/README is written in an unsupported language. File is not indexed.

0001 kioexec is launched when the user wants to open a remote file with
0002 an application that only supports local files.
0004 For this it does the following:
0005 - downloads a remote file to a temp location
0006 - starts a 'local' application with that temp file as argument
0007 - wait fors application to be exited
0008 - if the modification time of the file is different from the original one,
0009 (because the file was modified) then it offers re-uploading the modified version.
0010 This is how you offer network transparency to apps that don't have it.
0012 BUT: with KUniqueApplication, this breaks, because the app returns at once,
0013 so we have no way to know when the user finished editing the file...
0015 Conclusion: if the application has network transparency built-in, it should
0016 put "%u" in its desktop file - and kioexec isn't used -. If it doesn't, either
0017 it's a KApplication and kiiooexec does its job, or it's a KUniqueApplication
0018 and... kioexec can't see modifications to the file. Be warned.
0020 From Waldo: "The program doesn't return _at once_. It returns
0021 after "newInstance()" returns. So if you open the file there it will still work.
0022 (Or rename it)"
0024 David Faure <faure@kde.org>
0025 20-May-2000