Whenever you do any sort of file handling within the Vault client context, (moving multiple things, utilizing the copy design function, etc.) the process appears to be [get files from Vault] -> [do the thing] -> [send the files back to Vault].
This seems very unneccesary to me. Is there a way to make the Vault client run these operations on the Vault server in their entirety, so that Vault client never download anything unless unless you explicitly choose to do so, or open a file from within Vault client? Copying a design from one Vault subfolder to another shouldn't, in its nature, require any file transfer between the server and the client computer from which the command is run, other than the data needed to pass the neccesary commands for the operation to excecute (on the server).
If it worked that way, we'd probably get rid of the error messages relating to missing file references in the C:\windows\temp folder as well. Those tend to get annoying after a while...
In addition, this would be very time saving when you're working remotely from somewhere outside the local network the server resides in. What takes a matter of seconds to complete over the local network, takes a couple of minutes from outside...
