[OODT-194] Factor out Protocol infrastructure in PushPull into a separate component

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.2
• Fix Version/s: 0.4
• Component/s: push pull framework

Environment

none

• Assignee: Brian Foster
• Reporter: Brian Foster
• Created: 26/May/11 23:22
• Updated: 01/Mar/12 01:13
• Resolved: 01/Mar/12 01:13

Description

Refactoring will consist of two components: api and impl.

• API component will consist of the Protocol interface and all the helper classes so that API will be a usable component without forcing other components to inherit IMPL components dependencies
• IMPL component will depend on the API component and will have common implementation of the Protocol interface.

This refactoring will allow several new future feature capabilities:

• Filemgr can write a ProtocolBasedDataTransferer which depends on the API component (however users of the filemgr could then make their filemgr build depend on the IMPL and will, out of the box, support several different Protocol based transferers
• Distributed Pushpull jobs. A resource manager file downloading job can be implemented and will only depend on the protocol components without having to depend on pushpull component.

Initially i will be checking code into a branch: .../branches/protocol/cas-protocol-(api|impl)