oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Foster (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OODT-194) Factor out Protocol infrastructure in PushPull into a separate component
Date Thu, 26 May 2011 23:23:47 GMT
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

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 another computer to get all the implementations
dependencies sucked in
- 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 on and out of
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message