pipelining: deprecated #2705
pipelining: deprecated #2705
Conversation
bagder
added
next-feature-window
|
Cisco is a major vendor that has used pipelining, I believe that was discussed here or IRC or somewhere I don't remember. Also from professional experience Samsung is another. What they're using it in I don't know. This isn't an objection just pointing out there are companies that I assume are still using it. |
|
Sure, and that's a reason why we have a long period from us just disabling the feature until it gets removed so that people can notice and speak up and object if they feel this is a crucial feature for them. |
|
Just noting that this would make the naming of the Perhaps |
Sure, maybe we should consider adding an alias for the name, but with #2709 the option itself will be less needed and then I'm not sure it is as important anymore... |
bagder
force-pushed
the
bagder/deprecate-pipelining-step-1
branch
from
8296b89
to
e9444fe
Compare
Transparently. The related curl_multi_setopt() options all still returns OK when pipelining is selected. To re-enable the support, the single line change in lib/multi.c needs to be reverted.
bagder
force-pushed
the
bagder/deprecate-pipelining-step-1
branch
from
e9444fe
to
c46edab
Compare
bagder
removed
the
next-feature-window
Transparently. The related curl_multi_setopt() options all still returns OK when pipelining is selected. To re-enable the support, the single line change in lib/multi.c needs to be reverted. See docs/DEPRECATE.md Closes curl#2705
Transparently. The related curl_multi_setopt() options all still return OK when pipelining is selected.
To re-enable the support, the single line change in lib/multi.c needs to be reverted.
See DEPRECATE for the explanation and plan.