Set the long weight to a number between 1 and 256.
When using HTTP/2, this option sets the individual weight for this particular
stream used by the easy handle. Setting and using weights only makes
sense and is only usable when doing multiple streams over the same
connections, which thus implies that you use CURLMOPT_PIPELINING(3).
This option can be set during transfer and will then cause the updated weight
info get sent to the server the next time a HTTP/2 frame is sent to the
See section 5.3 of RFC 7540 for protocol details:
Streams with the same parent should be allocated resources proportionally
based on their weight. So if you have two streams going, stream A with weight
16 and stream B with weight 32, stream B will get two thirds (32/48) of the
available bandwidth (assuming the server can send off the data equally for