From 215baa74f709cd5026ea037eb9204cee93baa1bb Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 17 Oct 2019 10:05:53 +0200 Subject: curl: add --parallel-immediate Starting with this change when doing parallel transfers, without this option set, curl will prefer to create new transfers multiplexed on an existing connection rather than creating a brand new one. --parallel-immediate can be set to tell curl to prefer to use new connections rather than to wait and try to multiplex. libcurl-wise, this means that curl will set CURLOPT_PIPEWAIT by default on parallel transfers. Suggested-by: Tom van der Woerdt Closes #4500 --- docs/cmdline-opts/parallel-immediate.d | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 docs/cmdline-opts/parallel-immediate.d (limited to 'docs/cmdline-opts/parallel-immediate.d') diff --git a/docs/cmdline-opts/parallel-immediate.d b/docs/cmdline-opts/parallel-immediate.d new file mode 100644 index 000000000..343931085 --- /dev/null +++ b/docs/cmdline-opts/parallel-immediate.d @@ -0,0 +1,9 @@ +Long: parallel-immediate +Help: Do not wait for multiplexing (with --parallel) +Added: 7.68.0 +See-also: parallel parallel-max +--- +When doing parallel transfers, this option will instruct curl that it should +rather prefer opening up more connections in parallel at once rather than +waiting to see if new transfers can be added as multiplexed streams on another +connection. -- cgit v1.2.3