Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 22 Nov 2016 17:53:58 +0000 (UTC)
From: "Greg Mann (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12980831.1466425737000.341069.1479837238400@Atlassian.JIRA>
In-Reply-To: <JIRA.12980831.1466425737000@Atlassian.JIRA>
References: <JIRA.12980831.1466425737000@Atlassian.JIRA> <JIRA.12980831.1466425737752@arcas>
Subject: [jira] [Updated] (MESOS-5658) Socket::shutdown() is inconsistent
 with BSD sockets API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 22 Nov 2016 17:54:05 -0000


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

Greg Mann updated MESOS-5658:
-----------------------------
    Sprint: Mesosphere Sprint 47

> Socket::shutdown() is inconsistent with BSD sockets API
> -------------------------------------------------------
>
>                 Key: MESOS-5658
>                 URL: https://issues.apache.org/jira/browse/MESOS-5658
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess
>            Reporter: Neil Conway
>            Assignee: Greg Mann
>            Priority: Minor
>
> In libprocess, the {{Socket::shutdown()}} member function is inconsistent with the {{shutdown(2)}} function from the Berkeley sockets API: the former doesn't take any parameters (and implicitly *only* shuts down the receiver-side of the socket), whereas the latter takes a parameter that controls which side(s) are shutdown.
> IMO we should either make these behave the same or document why they are different.


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