chiark / gitweb /
max_queue_time: Doc that it is not LIMITed
authorIan Jackson <ijackson@chiark.greenend.org.uk>
Wed, 4 Aug 2021 22:31:35 +0000 (23:31 +0100)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Wed, 4 Aug 2021 22:31:35 +0000 (23:31 +0100)
This is more orthogonal to describe and simpler to implement (indeed
it is what we have impleented here).

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
README.config
src/config.rs

index aa493bb7a41db77108259cb2c167bb03a00cf661..dd7381dfd48d3f5821049b0c5f4ef8c0a78b5561 100644 (file)
@@ -99,10 +99,8 @@ Capped settings:
   max_queue_time
      Discard packets after they have been queued this long waiting
      for http.
-     On server: setting applies to downward packets, and is capped
-      by LIMIT values.
-     On client: setting applies to upward packets, and is
-      not affected by LIMIT values.
+     On server: setting applies to downward packets.
+     On client: setting applies to upward packets.
      [10 s; LIMIT: 121 s]
 
   http_timeout
index b1e27aa7a467d82e776f25621b55086ca6b566f0..a36ec584f987864a27bb2803ca553dce9d574dd8 100644 (file)
@@ -16,7 +16,7 @@ pub struct InstanceConfig {
 
   // Capped settings:
   #[limited]    pub max_batch_down:               u32,
-  #[limited]    pub max_queue_time:               Duration, // xxx client unlimited
+  #[limited]    pub max_queue_time:               Duration,
   #[limited]    pub http_timeout:                 Duration,
   #[limited]    pub target_requests_outstanding:  u32,