Change Details

There are two challenges here: 1.) The config of KIO workers is stored in a file "kioslaverc". That file is accessed by that name from multiple places, both for reading & writing. Ideally the file should be renamed to "kioworkerrc", to match the new lingo. 2.) The D-Bus signal by name "reparseSlaveConfiguration" from object path:"/KIO/Scheduler" with interface "org.kde.KIO.Scheduler" is emitted and listened for from multiple places, without being bound to a well-known DBus service name, and thus also not to a KF version.

There are two challenges here: 1.) The config of KIO workers is stored in a file "kioslaverc". That file is accessed by that name from multiple places, both for reading & writing. Ideally the file should be renamed to "kioworkerrc", to match the new lingo. 2.) The D-Bus signal by name "reparseSlaveConfiguration" from object path:"/KIO/Scheduler" with interface "org.kde.KIO.Scheduler" is emitted and listened for from multiple places, without being bound to a well-known DBus service name, and thus also not to a KF version. Ideally the signal should be renamed to "reparseWorkerConfiguration", to match the new lingo.

There are two challenges here: 1.) The config of KIO workers is stored in a file "kioslaverc". That file is accessed by that name from multiple places, both for reading & writing. Ideally the file should be renamed to "kioworkerrc", to match the new lingo. 2.) The D-Bus signal by name "reparseSlaveConfiguration" from object path:"/KIO/Scheduler" with interface "org.kde.KIO.Scheduler" is emitted and listened for from multiple places, without being bound to a well-known DBus service name, and thus also not to a KF version. Ideally the signal should be renamed to "reparseWorkerConfiguration", to match the new lingo.