Details
Description
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.
Attachments
Issue Links
- is a clone of
-
REEF-362 Implement a Wake Transport using HTTP
-
- Open
-