Version: 2+ (using KDE Devel) Installed from: Compiled sources OS: Linux My wish is that kget2 (the one on make_it_cool branch) will support an interface for remote control. In fact is should have a thread that listens for exernal connections and handle commands appropriately. So if there is kget on the "PC2_ADSL", and I am on "PC1_56K", I can control the remote kget from the one on the local pc and: - send transfers to the remote one (file->export->transfer list to remote kget...) - take control of the remote one (file->connect->remote kget...) and administer it via the local gui. (The MVC structure permits that). - watch downloads on the remote server (in additions to local ones). - more actions of this type but they must be really easy usability-wise (just a couple of clicks and you get connected and you know what you're doing). Go guys, Make IT COOL!!
Wouldn't the already implemented dcop functions provide at least the basics of this. ssh remote-server dcop kget KGet-Interface addTransfers(http://...., destDir); I don't know if it's a good idea to turn a GUI app into a server. The next feature people might want then is to make kget run without X and or KDE dependency, so they can run it on a remote server that does not have an X server. There are tools like wget and commandline versions of bittorrent for things like this.
KGet 2.1 has now a webinterface. Also, the D-Bus interface is very powerful now.