[jira] [Updated] (MESOS-5658) Socket::shutdown() is inconsistent with BSD sockets API
[
https://issues.apache.org/jira/browse/MESOS-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-5658:
-
Assignee: (was: Greg Mann)
> 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
>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)
[jira] [Updated] (MESOS-5658) Socket::shutdown() is inconsistent with BSD sockets API
[
https://issues.apache.org/jira/browse/MESOS-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-5658:
-
Sprint: (was: 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)
[jira] [Updated] (MESOS-5658) Socket::shutdown() is inconsistent with BSD sockets API
[
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)
