[
https://issues.apache.org/jira/browse/MESOS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178525#comment-14178525
]
Timothy St. Clair commented on MESOS-1330:
------------------------------------------
I like the updated design a lot more, nice work guys!
My only concern is that we may be creating Yet Another ~=
http://en.wikipedia.org/wiki/Proactor_pattern. Given the plethora of event
based communications libraries, it would be nice to denote the overall design
goals.
> Introduce stream abstraction to libprocess
> ------------------------------------------
>
> Key: MESOS-1330
> URL: https://issues.apache.org/jira/browse/MESOS-1330
> Project: Mesos
> Issue Type: Task
> Components: general, libprocess
> Reporter: Niklas Quarfot Nielsen
> Assignee: Joris Van Remoortere
> 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.3.4#6332)
