[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18363 [Core Tor/Tor]: Tor could use a publish/subscribe abstraction
#18363: Tor could use a publish/subscribe abstraction
-------------------------------------------------+-------------------------
Reporter: nickm | Owner: nickm
Type: enhancement | Status:
Priority: High | needs_revision
Component: Core Tor/Tor | Milestone: Tor:
Severity: Normal | 0.2.9.x-final
Keywords: modularity, tor-modularity, | Version:
TorCoreTeam201605, TorCoreTeam- | Resolution:
postponed-201604 | Actual Points:
Parent ID: | Points: medium
Reviewer: dgoulet | Sponsor:
| SponsorS-can
-------------------------------------------------+-------------------------
Comment (by nickm):
I fixed some of the simpler issues. I'm going to wontfix the following
ones:
* The static/public stuff. I think that I got it right, as cpunks
describes above, but it'll be easy enough to fix later if we need it
different.
* Function naming stuff; I don't mind the names. Also they're easy
enough to change later if somebody makes a patch.
* Yes, foo_subscriber_t is only a tag.
* Low-valued priorities meaning "do this first" is all over POSIX; I'm
not changing that.
That leaves these as my remaining items:
* Seeing if I can mess with the type definitions so that you don't need
to declare a struct for non-compound message types.
* The "interesting" interactions as described above.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18363#comment:16>
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