Opened 9 years ago

Closed 8 years ago

#252 closed enhancement (duplicate)

More flexibility for remote_config sets (callbacks)

Reported by: jelte Owned by: jelte
Priority: medium Milestone:
Component: configuration Version:
Keywords: msgq ccsession config modules Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket:
Total Hours: Internal?: no

Description

During the review of ticket #252, it came to the attention that remote config is a subset of that of 'local' config (you cannot specify callbacks when configuration of other modules changes, only for that of your own, so for remotes everything runs underwater, and you can only look what a value is the moment you need it).

We might want to add callback for remote module configuration changes to CCSession as well. Other possible solutions are mentioned in the comment, but this one seems most viable and usable.

Subtickets

Change History (4)

comment:1 Changed 9 years ago by jelte

  • billable set to 0
  • Internal? unset
  • Owner changed from jelte to UnAssigned
  • Status changed from new to assigned

comment:2 Changed 8 years ago by shane

  • Defect Severity set to N/A
  • Owner changed from UnAssigned to jelte
  • Sub-Project set to DNS

Jelte, I don't know which ticket the review is for. This ticket claims the review cam from itself. :-P

Anyway, I don't understand this issue, possibly because the other ticket is not correct. Is the idea to use the command bus to broadcast when configuration changes happen somehow, across the entire BIND 10 application (or interested subsets of it)?

comment:3 Changed 8 years ago by shane

  • Sub-Project changed from DNS to Core

comment:4 Changed 8 years ago by jelte

  • Resolution set to duplicate
  • Status changed from assigned to closed

Tried to find which ticket this one is talking about, can't seem to find it (perhaps it's one of the initial list of 'general code review' ones). But it doesn't actually matter, this has been implemented in #922 and #1010, so I'm closing it as a reverse dupe.

Note: See TracTickets for help on using tickets.