You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2014/11/14 18:53:33 UTC

[jira] [Updated] (MESOS-2109) Introduce socket factory

     [ https://issues.apache.org/jira/browse/MESOS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niklas Quarfot Nielsen updated MESOS-2109:
------------------------------------------
    Description: 
We need to be able to produce both SSL and Raw sockets in a configurable fashion. It cannot be either or, as we need an interim path during cluster upgrade where both types of sockets are available and can fall-back from encrypted to non-encrypted communication.

The idea would be to have something like Socket::create(flags). If more than one type is listed, we need to use the 'composable' socket (which is a wrapper object that enables the fallback mechanism)

> Introduce socket factory
> ------------------------
>
>                 Key: MESOS-2109
>                 URL: https://issues.apache.org/jira/browse/MESOS-2109
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Niklas Quarfot Nielsen
>
> We need to be able to produce both SSL and Raw sockets in a configurable fashion. It cannot be either or, as we need an interim path during cluster upgrade where both types of sockets are available and can fall-back from encrypted to non-encrypted communication.
> The idea would be to have something like Socket::create(flags). If more than one type is listed, we need to use the 'composable' socket (which is a wrapper object that enables the fallback mechanism)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)