[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [torspec/master] Fix Timestamp, to be the most recent result.
commit 8760c78ddcdb5d7a33b0d6322e82cb287cae6fcb
Author: juga0 <juga@xxxxxxxxxx>
Date: Tue May 22 08:51:54 2018 +0000
Fix Timestamp, to be the most recent result.
It is not the timestamp when the file was created.
---
bandwidth-file-spec.txt | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt
index c647aee..7db9eab 100644
--- a/bandwidth-file-spec.txt
+++ b/bandwidth-file-spec.txt
@@ -118,9 +118,18 @@ It consists of:
[At start, exactly once.]
- The Unix Epoch time in seconds when the file was created.
- It does not follow the KeyValue format for backwards
- compatibility with version 1.0.0.
+ The Unix Epoch time in seconds of the most recent generator result.
+
+ If there are multiple generators which can fail independently,
+ implementations SHOULD take the most recent timestamp from each
+ generator and use the oldest value. This ensures all the generators
+ continue running.
+
+ If there are scanners that do not run continuously, they SHOULD be
+ excluded from the timestamp calculation.
+
+ It does not follow the KeyValue format for backwards compatibility
+ with version 1.0.0.
"version=" version_number NL
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits