Class Http2Protocol.SettingIdentifier$.SETTINGS_MAX_CONCURRENT_STREAMS$

java.lang.Object
akka.http.impl.engine.http2.Http2Protocol.SettingIdentifier
akka.http.impl.engine.http2.Http2Protocol.SettingIdentifier$.SETTINGS_MAX_CONCURRENT_STREAMS$
All Implemented Interfaces:
Serializable, scala.Equals, scala.Product
Enclosing class:
Http2Protocol.SettingIdentifier$

public static class Http2Protocol.SettingIdentifier$.SETTINGS_MAX_CONCURRENT_STREAMS$ extends Http2Protocol.SettingIdentifier implements scala.Product, Serializable
SETTINGS_MAX_CONCURRENT_STREAMS (0x3): Indicates the maximum number of concurrent streams that the sender will allow. This limit is directional: it applies to the number of streams that the sender permits the receiver to create. Initially, there is no limit to this value. It is recommended that this value be no smaller than 100, so as to not unnecessarily limit parallelism.

A value of 0 for SETTINGS_MAX_CONCURRENT_STREAMS SHOULD NOT be treated as special by endpoints. A zero value does prevent the creation of new streams; however, this can also happen for any limit that is exhausted with active streams. Servers SHOULD only set a zero value for short durations; if a server does not wish to accept requests, closing the connection is more appropriate.

See Also: