[
https://issues.apache.org/jira/browse/MESOS-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909443#comment-14909443
]
Alex Clemmer commented on MESOS-3526:
-------------------------------------
Actually, it was [~jvanremoortere] who told me that this changes the behavior
significantly, so I'm not the best person to answer this question. That said
(in my limited experience) as I understand it, libevent supports I/O control
ports on Windows, which I'm told are much more performant than the alternatives
that libev uses.
Anyway, what we do know for sure is the libevent code path is much less
well-exercised, so we want to offer both code paths for users.
> Transition Windows from libevent to libev
> -----------------------------------------
>
> Key: MESOS-3526
> URL: https://issues.apache.org/jira/browse/MESOS-3526
> Project: Mesos
> Issue Type: Task
> Components: build
> Reporter: Alex Clemmer
> Assignee: Alex Clemmer
> Labels: build, cmake, mesosphere
>
> Right now we have to use libevent to compile Mesos on Windows because libev
> does not have a clean standalone build available on Windows. (We also use a
> beta version of libevent because it's easier to compile.)
> But, this changes the behavior of libprocess significantly. So, we need to
> think about transitioning to libev after MVP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
