BIND 10 #352: Improve Xfrout request handling strategy

BIND 10 Development do-not-reply at isc.org
Fri Oct 8 09:56:25 UTC 2010


#352: Improve Xfrout request handling strategy
------------------------------+---------------------------------------------
      Reporter:  zzchen_pku   |        Owner:  zzchen_pku
          Type:  enhancement  |       Status:  reviewing 
      Priority:  major        |    Milestone:            
     Component:  xfrout       |   Resolution:            
      Keywords:               |    Sensitive:  0         
Estimatedhours:  0.0          |        Hours:  0         
      Billable:  1            |   Totalhours:  1.5       
      Internal:  0            |  
------------------------------+---------------------------------------------

Comment(by zhanglikun):

 > >  - Related to the point of whether we have multiple instances, is it
 okay to make _is_shut_down and _read/write_sock class variables?  If I
 understana it correctly they will be shared by all instances, and I
 suspect it would cause undesirable effects.
 >
 > it's class variable, but it was used as self._is_shut_down, then the
 class variable will change to instance variable, so it will not cause
 undesirable effects. Also, this is what I learned from ThreadingMixIn() in
 python code.

 I just find I made a mistake, I will move these class variable to be
 object variable.

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


More information about the bind10-tickets mailing list