client: Make the queue size bounds configurable

[tattlekey] / client / config.c

diff --git a/client/config.c b/client/config.c
index 9bd216dba00dca5639c6e59e56e9391f3c7dbd71..0e1a86d29e6610f36ef110f8aa49ca848a18de29 100644 (file)
--- a/client/config.c
+++ b/client/config.c
@@ -24,4 +24,18 @@ u32_t config_minimum_seconds_between_button_presses = 1;
 
 /* Send each report multiple times. */
 uint config_resend_count = 5;
 
 /* Send each report multiple times. */
 uint config_resend_count = 5;

-u32_t config_resend_interval_ms = 1000;
+
+/* These control the size of the per-send-count press queues.
+When the button is pressed more than config_maximum_queue_size times
+within the resend interval, some presses will be reported fewer
+than config_resend_count times. This is usually fine because it's
+the old, longest-delayed, most-redundant reports that get dropped;
+fresh, timely reports of new button presses will not get anywhere near
+config_resend_count in a resend interval because the early resend internals
+are so short.  */
+uint config_maximum_queue_size = 512;
+
+/* This is paranoia about unanticipated delays.  Setting this to zero
+would probably be fine, but imposing a minimum queue size is an easy
+safety measure. */
+uint config_minimum_queue_size = 32;