[
https://issues.apache.org/jira/browse/MESOS-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958381#comment-14958381
]
Jian Qiu commented on MESOS-3570:
---------------------------------
This is due to that internal::request is a one-time connection, so we actually
may need pipelining abstraction in internal::request?
> Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess
> --------------------------------------------------------------------
>
> Key: MESOS-3570
> URL: https://issues.apache.org/jira/browse/MESOS-3570
> Project: Mesos
> Issue Type: Bug
> Reporter: Anand Mazumdar
> Labels: mesosphere, newbie
>
> Currently, the scheduler library sends calls in order by chaining them and
> sending them only when it has received a response for the earlier call. This
> was done because there was no HTTP Pipelining abstraction in Libprocess
> {{process::post}}.
> However once {{MESOS-3332}} is resolved, we should be now able to use the new
> abstraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
