[
https://issues.apache.org/jira/browse/MESOS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062595#comment-14062595
]
Niklas Quarfot Nielsen commented on MESOS-1330:
-----------------------------------------------
I have been working on a SSL port of libprocess lately and have now have a
couple of hard earned experiences with interfacing with libev and doing a
middle layer transport.
TL;DR I'd recommend to look into ways to replace libev all together with a
event system that supports SSL off-the-shelf. For example libuv or lib event.
In the case of SSL, SSL buffer state and socket state are not necessarily tied
(and is hard to do non-blocking fashion) and was very hard to play nicely in
libprocess.
That would also be a good time to clean up and document a bunch of libprocess
code.
Let me know what you think.
> Introduce connection/transport abstraction to stout
> ---------------------------------------------------
>
> Key: MESOS-1330
> URL: https://issues.apache.org/jira/browse/MESOS-1330
> Project: Mesos
> Issue Type: Improvement
> Components: general, libprocess
> Reporter: Niklas Quarfot Nielsen
> Labels: libprocess, network
>
> I think it makes sense to think in terms of different low or middle layer
> transports (which can accommodate channels like SSL). We could capture
> connection life-cycles and network send/receive primitives in a much explicit
> manner than currently in libprocess.
> I have a proof of concept transport / connection abstraction ready and which
> we can use to iterate a design.
> Notably, there are opportunities to change the current SocketManager/Socket
> abstractions to explicit ConnectionManager/Connection, which allow several
> and composeable communication layers.
> I am proposing to own this ticket and am looking for a shepherd to
> (thoroughly) go over design considerations before jumping into an actual
> implementation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
