From c37de908b1b2f2ea50aa53a7afa13d2c4cd785e1 Mon Sep 17 00:00:00 2001 From: Daniel Shapiro Date: Wed, 15 Jan 2020 14:40:16 -0800 Subject: [PATCH] Update README.md --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 5b3f530..812f61f 100644 --- a/README.md +++ b/README.md @@ -25,3 +25,12 @@ A local test run requires a broker to be actively running. Running:
`./gradlew run -Dexec.args="--broker http://localhost:8080/conn"` + +## Watch Group Logging Type Settings + +There are four possible values for the `Logging Type` of a watch group: +- `None`: Nothing will be logged +- `Interval`: Logging will happen on an interval (defined by the `Interval` setting) +- `All Data` and `Point Change`: Logging will happen for every update of the path's value + - The only difference between `All data` and `Point Change` is that `Point Change` will ignore an update if the value is the same as the last recorded value (in this run of the program). Since dglux only sends subscription updates on value changes (and once on the start of the subscription), this means there's not really any difference, aside from maybe some edge cases. + - Possibly important to note: Restarting the DSLink is not one of those edge cases. Both `All Data` and `Point Change` will record the initial value when the watch is started up, and so both will end up with a duplicate value in the database.