reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chanaka Balasooriya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-362) Implement a Wake Transport using HTTP
Date Sun, 05 Mar 2017 10:32:32 GMT

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

Chanaka Balasooriya commented on REEF-362:
------------------------------------------

Hi,
I am Chanaka Balasooriya, final year undergraduate at University of Moratuwa,Sri Lanka. I've
been working on Transport and similar technologies such as NIO, Pass-through and Apache Netty
library during my internship. So this project seems more interesting to me for GSoC-2017 and
I would like to know more about this. Could you please explain little bit more about what
we have to do in this project? 
Thanks,

> Implement a Wake Transport using HTTP
> -------------------------------------
>
>                 Key: REEF-362
>                 URL: https://issues.apache.org/jira/browse/REEF-362
>             Project: REEF
>          Issue Type: Improvement
>          Components: Wake, Wake.NET
>            Reporter: Markus Weimer
>              Labels: GSoC, gsoc2017
>
> Wake currently uses TCP connections for its messages. This is fast and efficient, but
provides challenges in some network environments. Also, it is considerable work to support
authentication and encryption.
> We could provide HTTP(S) as an alternative protocol for Wake. This transport will likely
be less efficient than the current path, but gain in security. And for the relatively small
messages used by the REEF control flow, the trade-off is likely worth it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message