BIND 10 #1987: 'wait for' command in bindctl execute handling (or something similar)

[BIND 10 Development]

#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:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jelte):

 at its very core, the problem is the RESTful-like nature of the
 communication between bindctl and cmdctl, and/or the state bindctl keeps
 to immediately error if you are trying to send something to a module that
 is not running (or change its configuration, originally it allowed for
 configuration of unknown modules but that was considered a defect as
 well).

 The problem could be circumvented by another thing; do full updates of
 bindctl by querying what is running between each and every command
 (similar to what it does in interactive mode), but that is quite an
 expensive operation. I originally thought that having some form of 'give
 me all changes since last time I asked' might be a solution here, but that
 would break the statelessness of cmdctl as well.

 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.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1987#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development