client: Make the queue size bounds configurable

[tattlekey] / client / config.c

diff --git a/client/config.c b/client/config.c
index a8e58440dff1b24d52829f6f8989d9afc0b332ac..0e1a86d29e6610f36ef110f8aa49ca848a18de29 100644 (file)
--- a/client/config.c
+++ b/client/config.c
@@ -1,19 +1,41 @@
 #include "config.h"
 
 /* Wi-Fi credentials */
-char wifi_ssid[] = "THEWIFISSID";
-char wifi_pass[] = "THEWIFIPASSWORD";
+char config_wifi_ssid[] = "THEWIFISSID";
+char config_wifi_pass[] = "THEWIFIPASSWORD";
 
 /* Network address of the server to contact */
-char tattle_server_ip_address[] = "192.168.10.10";
-u16_t tattle_port = 29803; // 'tk'
+char config_tattle_server_ip_address[] = "192.168.10.10";
+u16_t config_tattle_port = 29803; // 'tk'
 
 /* For distinguishing reports from multiple tattlekey devices. */
-u16_t this_tattler_identity = 1;
+u16_t config_this_tattler_identity = 1;
 
 /* Which GPIO pin is the button connected to?
  * The button should span this pin and ground, connecting this pin to ground
  * when pressed.
  * https://projects.raspberrypi.org/en/projects/introduction-to-the-pico/10
  * recommends pins 18, 22, or 28. */
-uint button_pin = 18;
+uint config_button_pin = 18;
+
+/* Don't bother reporting each separate button press when it is pressed many
+ * times in short succession.  (We also use this to de-bounce. :) */
+u32_t config_minimum_seconds_between_button_presses = 1;
+
+/* Send each report multiple times. */
+uint config_resend_count = 5;
+
+/* 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;