You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Brian Foster (JIRA)" <ji...@apache.org> on 2011/05/27 01:23:47 UTC
[jira] [Created] (OODT-194) Factor out Protocol infrastructure in
PushPull into a separate component
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
[jira] [Updated] (OODT-194) Factor out Protocol infrastructure in
PushPull into a separate component
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Foster updated OODT-194:
------------------------------
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)
was:
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)
> 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 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
[jira] [Issue Comment Edited] (OODT-194) Factor out Protocol
infrastructure in PushPull into a separate component
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (OODT-194) Factor out Protocol infrastructure in
PushPull into a separate component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040747#comment-13040747 ]
Chris A. Mattmann commented on OODT-194:
----------------------------------------
+1, this sounds like a great idea, Brian! I'll be interested to see how it comes along...
> 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 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
[jira] [Resolved] (OODT-194) Factor out Protocol infrastructure in
PushPull into a separate component
Posted by "Brian Foster (Resolved) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (OODT-194) Factor out Protocol infrastructure in
PushPull into a separate component
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063461#comment-13063461 ]
Brian Foster commented on OODT-194:
-----------------------------------
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
[jira] [Updated] (OODT-194) Factor out Protocol infrastructure in
PushPull into a separate component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-194:
-----------------------------------
Fix Version/s: 0.4
> 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