BIND 10 #2738: Clarify high-level design of the CC protocol
BIND 10 Development
do-not-reply at isc.org
Fri Apr 26 07:05:15 UTC 2013
#2738: Clarify high-level design of the CC protocol
-------------------------------------+-------------------------------------
Reporter: vorner | Owner:
Type: task | jinmei
Priority: medium | Status:
Component: Inter-module | reviewing
communication | Milestone:
Keywords: | Sprint-20130423
Sensitive: 0 | Resolution:
Sub-Project: DNS | CVSS Scoring:
Estimated Difficulty: 5 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
I think the document is now almost okay for merge. There are probably
something still missing (and I personally wanted to see a bit more
details on how to show the interest in getting subscriber changes),
but I'm already quite familiar with the concepts myself and it's now
difficult to figure out what the first time readers would miss.
There are also some minor points:
- The session/Group management: I assume subscribe/unsubscribe are
"fast" operations, and would clarify that.
- Users: in general, "client(s)" should probably be "user(s)" in this
section for terminology consistency.
- Users: I believe "The creates" should be either "The user creates"
or "It creates":
{{{
* The creates one or more sessions (there may be technical reasons to
have more than one session, such as threads, but it is not required
by the system).
}}}
I don't think I need to re-review these points. So, after fixing them
please merge and close the ticket.
--
Ticket URL: <http://bind10.isc.org/ticket/2738#comment:20>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list