[
https://issues.apache.org/jira/browse/OODT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Foster resolved OODT-194.
-------------------------------
Resolution: Fixed
integration to pushpull was done in OODT-367
> Factor out Protocol infrastructure in PushPull into a separate component
> ------------------------------------------------------------------------
>
> Key: OODT-194
> URL: https://issues.apache.org/jira/browse/OODT-194
> Project: OODT
> Issue Type: Improvement
> Components: push pull framework
> Affects Versions: 0.2
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.4
>
>
> 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)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
