Blame doc/nghttp2_option_set_peer_max_concurrent_streams.rst
|
Packit Bot |
4c90e1 |
|
|
Packit Bot |
4c90e1 |
nghttp2_option_set_peer_max_concurrent_streams
|
|
Packit Bot |
4c90e1 |
==============================================
|
|
Packit Bot |
4c90e1 |
|
|
Packit Bot |
4c90e1 |
Synopsis
|
|
Packit Bot |
4c90e1 |
--------
|
|
Packit Bot |
4c90e1 |
|
|
Packit Bot |
4c90e1 |
*#include <nghttp2/nghttp2.h>*
|
|
Packit Bot |
4c90e1 |
|
|
Packit Bot |
4c90e1 |
.. function:: void nghttp2_option_set_peer_max_concurrent_streams(nghttp2_option *option, uint32_t val)
|
|
Packit Bot |
4c90e1 |
|
|
Packit Bot |
4c90e1 |
|
|
Packit Bot |
4c90e1 |
This option sets the SETTINGS_MAX_CONCURRENT_STREAMS value of
|
|
Packit Bot |
4c90e1 |
remote endpoint as if it is received in SETTINGS frame. Without
|
|
Packit Bot |
4c90e1 |
specifying this option, the maximum number of outgoing concurrent
|
|
Packit Bot |
4c90e1 |
streams is initially limited to 100 to avoid issues when the local
|
|
Packit Bot |
4c90e1 |
endpoint submits lots of requests before receiving initial SETTINGS
|
|
Packit Bot |
4c90e1 |
frame from the remote endpoint, since sending them at once to the
|
|
Packit Bot |
4c90e1 |
remote endpoint could lead to rejection of some of the requests.
|
|
Packit Bot |
4c90e1 |
This value will be overwritten when the local endpoint receives
|
|
Packit Bot |
4c90e1 |
initial SETTINGS frame from the remote endpoint, either to the
|
|
Packit Bot |
4c90e1 |
value advertised in SETTINGS_MAX_CONCURRENT_STREAMS or to the
|
|
Packit Bot |
4c90e1 |
default value (unlimited) if none was advertised.
|