watch-dir setting to libtransmission

[Elbandi]

Every client has the watch-dir feature, but the necessary settings are loaded by themselfes. Could you move the load/save codes to libtransmission (and add to RPC too)?

[charles]

What would be the advantage of this?

[Elbandi]

​http://code.google.com/p/transmission-remote-dotnet/issues/detail?id=151

[charles]

IMO when you're talking about watch directories in one of the remote apps, what you'd really want is a watchdir on the remote client's system... since if you're downloading torrents from a web browser on that client system, that's where the files would be saved. That's not something that RPC can handle... all it would do is handle configuring the watchdir on the server.

Also, adding the watchdir feature to libtransmission would cause all kind of problems for the GTK+ and Mac clients.

I think the effort for this feature is not worth the benefits. To me the real watchdir feature in a remote client is something that would be implemented by the client to run on the client's system.

[Elbandi]

Replying to charles:

Also, adding the watchdir feature to libtransmission would cause all kind of problems for the GTK+ and Mac clients.

No-no. Not the whole watchdir feature move to libtransmission, move only the settings load/save things to libtransmission (so clients can configure watchdir over rpc, like configure download-dir @ Session-Set)

[livings124]

Having settings for gui-level features seems like a bad idea. For one thing, what if the gui doesn't implement it, or implements it in a different way?

[charles]

All the guis implement it in different ways. I really don't like this idea... it's a can of worms for (imo) not much payoff