[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #15648 [Ooni]: Create Protobufs for OONI's test reports
#15648: Create Protobufs for OONI's test reports
-------------------------------------------------+-------------------------
Reporter: isis | Owner: hellais
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Ooni | Version:
Keywords: ooni, ooni-pipeline, protobufs, | Actual Points:
bridgedb-parsers | Points:
Parent ID: |
-------------------------------------------------+-------------------------
I am worried that randomly adding/removing/changing fields in the .yamloo
OONI test report files is going to break report parsers in horrible ways.
And YAML doesn't have the safest track history for its parsers either.
Perhaps we could have something like [https://developers.google.com
/protocol-buffers/docs/overview Protobufs] for guaranteed
marshaling/unmarshaling/parsing of report data? Setting up Protobufs for
the reports would establish requirements, for example, that field names
and data types/representations can't just randomly change in the future,
at least not without bumping up the version for the report Protobuf (and
thus regenerating the parsers/marshalers) and maintaining backwards-
compatibility.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15648>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs