The time period in milliseconds that an open HTTP connection has to be idle before automatically being closed.
The time period in milliseconds that an open HTTP connection has to be idle before automatically being closed. Set to zero to disable connection timeouts.
Default: 10,000 ms = 10 seconds
The configuration of the spray-can message parser.
The configuration of the spray-can message parser.
The size of the read buffer used for processing incoming messages.
The size of the read buffer used for processing incoming messages. Usually there should be little reason to configure it to a value different from its default of 8192 (bytes).
The reapingCycle
is the time in milliseconds between two runs of the "reaper", which is the logic that closes
open HTTP connections whose idle timeout has exceeded the configured value.
The reapingCycle
is the time in milliseconds between two runs of the "reaper", which is the logic that closes
open HTTP connections whose idle timeout has exceeded the configured value. Larger values (very slightly) increase
overall server or client efficiency (since less time is being spent looking for timed out connections) whereas
smaller values increase the precision with which idle connections are really closed after the configured idle
timeout. The default value is 500, which means that the reaper runs twice per second.
The time period in milliseconds that are response has to be produced by the application (in the case of the ServerConfig) or received by the server (in the case of the ClientConfig.
The time period in milliseconds that are response has to be produced by the application (in the case of the ServerConfig) or received by the server (in the case of the ClientConfig. Set to zero to disable request timeouts. The default value is 5000 ms = 5 seconds.
The timeoutCycle
is the time in milliseconds between two runs of the logic that determines which of all open
requests have timed out.
The timeoutCycle
is the time in milliseconds between two runs of the logic that determines which of all open
requests have timed out. Larger values (very slightly) increase overall server or client efficiency (since less
time is being spent looking for timed out requests) whereas smaller values increase the precision with which
timed out requests are really reacted on after the configured timeout time has elapsed.
The default value is 200.
The common configuration elements of a ServerConfig and a ClientConfig.