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

Comment (by jinmei):

 I don't fully understand the issue and the proposed solution, but from
 a quick read this sounds like a dirty quick hack (like waiting for
 some arbitrary period and hoping everything will be fine).  Is my
 understanding correct, and are we going to solve it in a cleaner way
 in a near future (TM)?  And, in that case, isn't it possible that we
 wait until we have time for the cleaner solution than spending time
 for a hack?  Or, am I misunderstanding the nature of the proposal and
 it's actually cleaner than I thought?

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


More information about the bind10-tickets mailing list