#28226: Backend for an async publish-subcribe messaging system for cross-module communications -------------------------------------------------+------------------------- Reporter: nickm | Owner: nickm Type: enhancement | Status: | needs_revision Priority: Medium | Milestone: Tor: | 0.4.1.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-pubsub, sponsor31-maybe, | Actual Points: network-team-roadmap-2019-Q1Q2 | Parent ID: | Points: 8 Reviewer: catalyst | Sponsor: | Sponsor31-must -------------------------------------------------+------------------------- Changes (by catalyst):
* status: needs_review => needs_revision Comment: I wrote a proof of concept hooking up part of the new bootstrap reporting code to pubsub. https://github.com/tlyu/tor/tree/bootpubsub It builds but doesn't pass tests, because I haven't yet figured out how to hook up the pubsub mainloop stuff. I commented in the pull request about most of difficulties I experienced with the code and consuming-developer documentation. There are a few more, but I think they're minor documentation issues. I have some comments on architecture and design that it might not be worth delaying integration to address. I'll write them up soon. How much work is it to finish hooking up pubsub to the mainloop and initialization code? Would you be willing to add commits to do that? It would be great to be able to test my POC. Thanks. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28226#comment:15> 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