DBTManager, HCIHandler, GATTHandler: Have all timeout+ config values read from environment via DBTEnv

Only default value change:
- GATTHandler::L2CAP_READER_THREAD_POLL_TIMEOUT: 3s -> 10s (aligning w/ others)
- GATTHandler::GATT_WRITE_COMMAND_REPLY_TIMEOUT: Back to 500ms default like GATT_READ_COMMAND_REPLY_TIMEOUT

Using int32_t timeout, i.e. 31 bits suitable for extreme maximum.

1 files changed, 8 insertions, 8 deletions

diff --git a/api/direct_bt/DBTManager.hpp b/api/direct_bt/DBTManager.hpp
index f5e75d7a..c5a7de18 100644
--- a/api/direct_bt/DBTManager.hpp
+++ b/api/direct_bt/DBTManager.hpp
@@ -59,18 +59,18 @@ namespace direct_bt {
      */
     class DBTManager : public JavaUplink {
         public:
-            enum Defaults : int {
+            enum Defaults : int32_t {
                 /* BT Core Spec v5.2: Vol 3, Part F 3.2.8: Maximum length of an attribute value. */
                 ClientMaxMTU = 512,
-
-                /** 10s poll timeout for mgmt reader thread */
-                MGMT_READER_THREAD_POLL_TIMEOUT = 10000,
-                /** 3s timeout for mgmt command replies */
-                MGMT_COMMAND_REPLY_TIMEOUT = 3000,
-                /** Small ringbuffer capacity for synchronized commands */
-                MGMTEVT_RING_CAPACITY = 64
             };
 
+            /** Poll timeout for mgmt reader thread, defaults to 10s. */
+            static const int32_t MGMT_READER_THREAD_POLL_TIMEOUT;
+            /** Timeout for mgmt command replies, defaults to 3s. */
+            static const int32_t MGMT_COMMAND_REPLY_TIMEOUT;
+            /** Small ringbuffer capacity for synchronized commands, defaults to 64 messages. */
+            static const int32_t MGMTEVT_RING_CAPACITY;
+
             static const pid_t pidSelf;
 
         private: