[
https://issues.apache.org/jira/browse/MESOS-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu updated MESOS-4853:
--------------------------
Description:
Reference:
https://curl.haxx.se/libcurl/c/libcurl-multi.html
Currently, some URI fetchers rely on 'curl' command directly (using
subprocess). This is not ideal. The libcurl easy interface is blocking, so it
does not compose well with our async environment. However, the multi interface
seems to be suitable for our async environment. The tricky part is that we need
to hook the fd selecting logic with our underlying libev/libevent runtime, but
this should be doable.
was:
Reference:
https://curl.haxx.se/libcurl/c/libcurl-multi.html
Currently, some URI fetchers rely on 'curl' command directly (using
subprocess). This is not ideal. The libcurl easy interface is blocking, so it
does not compose well with our async environment. However, the multi interface
seems to be suitable for our async environment. The tricky part is that we need
to hook the fd selecting logic with our underlying libev/libevent runtime.
> Considering using libcurl multi interface to implement 'curl' in Mesos.
> -----------------------------------------------------------------------
>
> Key: MESOS-4853
> URL: https://issues.apache.org/jira/browse/MESOS-4853
> Project: Mesos
> Issue Type: Improvement
> Reporter: Jie Yu
>
> Reference:
> https://curl.haxx.se/libcurl/c/libcurl-multi.html
> Currently, some URI fetchers rely on 'curl' command directly (using
> subprocess). This is not ideal. The libcurl easy interface is blocking, so it
> does not compose well with our async environment. However, the multi
> interface seems to be suitable for our async environment. The tricky part is
> that we need to hook the fd selecting logic with our underlying
> libev/libevent runtime, but this should be doable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
