BIND 10 #1987: 'wait for' command in bindctl execute handling (or something similar)
BIND 10 Development
do-not-reply at isc.org
Tue May 29 17:31:27 UTC 2012
#1987: 'wait for' command in bindctl execute handling (or something similar)
-------------------------------------+-------------------------------------
Reporter: jelte | Owner:
Type: task | Status: new
Priority: | Milestone: Next-Sprint-
medium | Proposed
Component: bind- | Resolution:
ctl | Sensitive: 0
Keywords: | Sub-Project: Core
Defect Severity: N/A | Estimated Difficulty: 9
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:3 jelte]:
> So the proposed solution is to do regular updates, but only when
explicitely told to (by said 'wait for' command). The thing I had in mind
was, for instance, ask every 100 milliseconds, until the module has
appeared, and give up after 5 seconds (because you do need to give up and
present an error at some point). This may be considered a hack, but I am
not aware of any current proposal to change the fundamental nature of the
communication between bindctl and cmdctl.
Okay, so this seems to suggest that we'll need to clarify the
requirements to bindctl and possibly redesign how it works (even if
the end result is something similar to the 100ms and 5sec things, I
think it should be realized based on some general polling framework).
And, in that case, it will require more time than solving this
particular issue. If we want to solve the particular problem at a
higher priority, I'm okay with introducing a bandaid type of fix for
now.
--
Ticket URL: <http://bind10.isc.org/ticket/1987#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list