Hi Grant,
#define CLEANUP_TIMEOUT 8 /* in seconds */
#define INACTIVE_TIMEOUT 12 /* in seconds */
-#define MAXIMUM_RETRIES 4
+#define MAXIMUM_RETRIES 2
#define BGSCAN_DEFAULT "simple:30:-45:300"
#define AUTOSCAN_DEFAULT "exponential:3:300"
Julien:
NACK. IIRC, this value has been adjusted up and down through several iterations
and four was arrived at as being reasonable based on quite a bit of testing.
Please check the GIT history and follow-up on those changes to ensure this
doesn't reintroduce regressions that we've already been through on this value.
I don't remember choosing very thoroughly such value ;)
since I did the patch (commit f223d6ca519f509748a5bd53cf01f99e6b62ff8c)
Have to check my irc logs a bit more, couldn't retrieve anything about that.
I don't think it won't harm much lowering to 2. In the worst case, the
user will retry by himself.
The reason of this retries limit was due to "fuzzy factors" like weak
signal, AP not ready (or crappy firmware like too often...) etc...
So here, it's much about preference: which use case we prefer to help?
Cheers,
Tomasz
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
