Loading
Parse BandwidthFile body
Huh. That was easy. Our spec is pretty sparse on what our body includes, mandating that each line is a series of key=value pairs and includes a 'node_id' but not much beyond that. Minimal specificity limits what our parser can provide, but also grants sbws flexability and makes my work dead easy. Body content is vended to users as a mapping of relay fingerprints to measurement metadata without any additional processing (no mandatory fields, type casting, etc).