Transmission Remote GUI will timeout and lose connection when using Set Location

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install Transmission on a machine with multiple drives
2. Point Transmission Remote GUI to that instance of Transmission
3. Move location on a downloaded file from one drive to another.  (This appears 
to be dependent on filesize.  Happens nearly 100% of the time on files over 1GB 
in size)
4. The file will successfully move and the GUI will reconnect to Transmission 
after the process has completed on the server.

What is the expected output? What do you see instead?

I would expect the Transmission Remote GUI to maintain the connection even if 
actions cannot be completed during the move process.

What version of the product are you using? On what operating system?

transgui-4.1-setup.exe; Windows 7 x64

Please provide any additional information below.

I don't know if this is a factor or not since I don't have any way to test it.  
The machine running Transmission is a single core processor (built specifically 
that way to reduce power usage).  It is possible that a dual core processor 
would maintain the connection, but I don't have any way to verify.

I'm just wondering if this is expected behavior for the GUI or if this is a 
problem that should be addressed.

Thanks.

Original issue reported on code.google.com by dk...@xmission.com on 27 Sep 2013 at 9:34

[GoogleCodeExporter]

It's a well known bug/limitation of Transmission. The file move operation is 
performed in the same thread as the other tasks, including RPC server.

Original comment by j...@cp-lab.com on 28 Sep 2013 at 8:21

• Changed state: TransmissionBug

[GoogleCodeExporter]

This makes sense and sort of what I expected.  Any chance that the GUI could 
have an adjustable timeout setting, so that it would wait as long as I need it 
to without generating an error?

Thanks.

Original comment by dk...@xmission.com on 3 Oct 2013 at 1:36