You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2017/09/01 21:25:00 UTC
[jira] [Commented] (MESOS-6770) Handle SSL socket read and write
events separately
[ https://issues.apache.org/jira/browse/MESOS-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151166#comment-16151166 ]
Benjamin Mahler commented on MESOS-6770:
----------------------------------------
It appears these are not set when using SSL. However, this was fixed in libevent 2.1:
https://github.com/libevent/libevent/blob/e7ff4ef2b4fc950a765008c18e74281cdb5e7668/whatsnew-2.1.txt#L333-L335
> Handle SSL socket read and write events separately
> --------------------------------------------------
>
> Key: MESOS-6770
> URL: https://issues.apache.org/jira/browse/MESOS-6770
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
> Reporter: Greg Mann
> Labels: libprocess, socket, ssl
>
> The SSL socket code in libprocess currently does not distinguish between events received during reading and those received during writing. However, libevent does provide event flags with this information: {{BEV_EVENT_READING}} and {{BEV_EVENT_WRITING}}. We should make use of these flags to handle read and write events differently.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)