Bug 165890 - [api] Supertransfer should be registered per system type
Summary: [api] Supertransfer should be registered per system type
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: dsdp.tm.rse-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on: 256587
Blocks:
  Show dependency tree
 
Reported: 2006-11-27 04:40 EST by Martin Oberhuber CLA
Modified: 2008-11-26 05:00 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2006-11-27 04:40:49 EST
Each SystemType should be able to register the kinds of supertransfer (zip, tar or other) that it supports.

This would allow that during a Copy operation, the source and target system types could do a "handshake" in order to try and find a kind of supertransfer that they both support. When they find one, this supertransfer can be used in order to speed up the transfer, and allow for file permissions to be retained.

The current way of allowing the user to set the supertransfer mode in the Preferences does not scale to lots of different kinds of systems.

The proposed solution would scale and also eliminate the need for the user to select a kind of supertransfer.

Note that we may want to be able and register additional kinds of supertransfer for an existing system type later on, as a kind of "add-on". For any system type that supports a shell, the supertransfer can be registered by adding a set of shell commands that perform the compress and expand operations, and a method for getting a suitable archive name.
Comment 1 Martin Oberhuber CLA 2006-11-27 04:44:03 EST
Addition of supertransfer as proposed would support the "copy permission bits across systems" use-case as described in bug 165891.
Comment 2 Martin Oberhuber CLA 2007-05-18 16:06:10 EDT
Not for 2.0