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] [Issue Comment Edited] (OODT-194) Factor out Protocol infrastructure in PushPull into a separate component
Date Mon, 11 Jul 2011 18:29:00 GMT

    [ https://issues.apache.org/jira/browse/OODT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063461#comment-13063461
] 

Brian Foster edited comment on OODT-194 at 7/11/11 6:27 PM:
------------------------------------------------------------

first part of issue commited to trunk (r1145272)... next step: integrating it into pushpull

      was (Author: bfoster):
    first part of issue commited to trunk... next step: integrating it into pushpull
  
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message