[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28684 [Core Tor/sbws]: Make sbws easy to understand and maintain
#28684: Make sbws easy to understand and maintain
---------------------------+-----------------------------------
Reporter: juga | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: sbws: unspecified
Component: Core Tor/sbws | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------+-----------------------------------
Comment (by juga):
Replying to [comment:7 irl]:
> If the file format is changing, and refactoring things is something you
have time for, adding a bandwidth list formatter and parser to stem would
allow it to be used in sbws and then also in bushel. There won't be any
inter-op testing so we're more likely to miss bugs in spec compliance but
there would be reduced code maintenance.
This sounds a good idea. I think that implementing the bandwidth file
parsing in stem is just mostly copy-pasting what we implemented in sbws
(without the scaling part and parsing results, it's not too complex nor
too much code0.
So, maybe instead of renaming the keys, as soon as there's time (in 1/2
weeks), i could try this. Later we can rename the keys there.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28684#comment:9>
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