Yabi-be Recursive copy through backends needs to be more efficient

[GoogleCodeExporter]

Connection setup and teardown is killing recursive copy speed of very large 
file trees. This needs to be fixed by doing the entire rcopy in a single 
connection instance.

Original issue reported on code.google.com by ahunter.ccg@gmail.com on 6 Jul 2011 at 8:55

[GoogleCodeExporter]

Original comment by aahun...@gmail.com on 29 Jul 2011 at 2:58

• Changed title: Yabi-be Recursive copy through backends needs to be more efficient

[GoogleCodeExporter]

This is difficult because of the file transfer is fifo based. I suggest a targz 
service be built into the fs backends similar to the ls/rm/mkdir functions.  It 
returns a stream of a bundle of files tar gz encoded. After this recursive copy 
in a single connection is easy. If a backend can't support targz in any way, 
then it can fall back to the old rcopy method. This also paves the way for 
front end directory downloads.

Original comment by retrogra...@gmail.com on 24 May 2012 at 2:10

[GoogleCodeExporter]

Original comment by aahun...@gmail.com on 7 Jul 2012 at 3:42

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

implemented by connecting tgz streams together via zput/zget in branch 
cwellington-4 rev: a15db9ec4a81

Original comment by retrogra...@gmail.com on 19 Sep 2012 at 3:36

• Changed state: Fixed