You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/08/06 23:31:04 UTC

[jira] [Commented] (REEF-350) Removing code duplication in Wake and GroupCommunication

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

Markus Weimer commented on REEF-350:
------------------------------------

[~dkm2110], is this still an issue? I believe you've cleaned this up along the way, right?

> Removing code duplication in Wake and GroupCommunication
> --------------------------------------------------------
>
>                 Key: REEF-350
>                 URL: https://issues.apache.org/jira/browse/REEF-350
>             Project: REEF
>          Issue Type: Improvement
>          Components: GroupCommunications, Wake.NET
>         Environment: .NET
>            Reporter: Dhruv Mahajan
>
> Right now Wake Layer and Group Communication Layer is going through changes for efficiency and removing data copying multiple times [REEF-179]. Currently we have internal IWritable implementation for Wake and IStreamingCodec API at group communication side. There is lot of code duplication between the old and new APIs.
> We aim to do the two following things:
>   # Convert IWritable interface in Wake and Network Service layer to IStreamingCodec.
>   # Remove the old code based on Codec and retain the external facing APIs for backward compatibility. However beneath these old APIs the new IStreamingCodec based implementation will be running. We will provide an internal ICodec to IStreamingCodec converter to maintain the backward compatibility in case user still wants to give the ICodec interface for messages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)