mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kone (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1330) Introduce connection/transport abstraction to stout
Date Tue, 23 Sep 2014 03:31:34 GMT

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

Vinod Kone commented on MESOS-1330:
-----------------------------------

It would be great if you can write some benchmark tests for libprocess as part of this effort
to ensure we are not losing performance. See registrar_tests.cpp in mesos for an example.

> 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.3.4#6332)

Mime
View raw message