#20228: Append all votes with same valid-after time to a single file in
`recent/`
-------------------------------+---------------------
Reporter: karsten | Owner:
Type: enhancement | Status: new
Priority: High | Milestone:
Component: Metrics/CollecTor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------+---------------------
Comment (by iwakeh):
Thanks for the history here! Parts like `rsync` to `recent` could be
guessed from the code, but its good to have it confirmed. And, for other
topics like the purpose of 'recent' it is very important and an easy read
:-)
Well, so the definition/purpose for/of `recent` is:
Provide the latest subset of descriptors a CollecTor could acquire, where
'latest' is currently defined as three days or more current acquisition
time, which can be download time or sync-time (once sync is in place).
Following this definition your second suggestion to store all descriptors
in 'recent' bundled according to their acquisition time is a simple
consequence.
It just needs to be stated prominently somewhere that recent is not for
human-readable browsing.
(The database should not be too difficult to be supplied here soon.)
How to approach the implementation?
I'd like to have this implementation in order to simplify merging and some
of the existing CollecTor code.
I could implement it together with the sync ticket (with decent commits
for review). That also would be a big step forward in modularizing the
Collector code and making it testable etc.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20228#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
