reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-362) Implement a Wake Transport using HTTP
Date Thu, 09 Mar 2017 23:53:38 GMT

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

Markus Weimer commented on REEF-362:
------------------------------------

Wake at its core uses a {{RemoteMananager}} implementation to send messages. In the current
implementation, it sends messages via a custom RPC protocol implemented on top of Netty in
Java and raw sockets in .NET. The idea of this JIRA is to make a new implementation which
instead relies on HTTP(S) for that message exchange.

[~chanaka balasooriya], does this answer your question?

> 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