You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Kim Doyoung (JIRA)" <ji...@apache.org> on 2017/05/25 07:25:04 UTC

[jira] [Commented] (REEF-362) Implement a Wake Transport using HTTP

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

Kim Doyoung commented on REEF-362:
----------------------------------

To implement Wake Transport via HTTP, I'm thinking of using an external library for HTTP. 

I think Apache HttpComponents is one of available options.

Is there any suggestion about what library is appropriate for this?


> 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)