From e9c7f9b95d490aea3f0f213d4666d2dbf7e2111c Mon Sep 17 00:00:00 2001
From: geeksville <kevinh@geeksville.com>
Date: Sat, 30 May 2020 19:04:33 -0700
Subject: [PATCH] tell the phone what the current worst case message timeout is

---
 mesh.proto | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/mesh.proto b/mesh.proto
index c9246aa..df9a02b 100644
--- a/mesh.proto
+++ b/mesh.proto
@@ -567,6 +567,11 @@ message MyNodeInfo {
   Old device loads (older that 0.6.5 do not populate this field, but all newer loads do). */
   uint32 node_num_bits = 12;
 
+  /** How long before we consider a message abandoned and we can clear our caches of any messages in flight
+  Normally quite large to handle the worst case message delivery time, 5 minutes.  Formerly called FLOOD_EXPIRE_TIME in the device code
+  */
+  uint32 message_timeout_msec = 13;
+
   /// FIXME - add more useful debugging state (queue depths etc)
 }