BIND 10 #407: Support for handling multiple requests concurrently

[BIND 10 Development]

#407: Support for handling multiple requests concurrently
---------------------------+------------------------------------------------
  Reporter:  zzchen_pku    |            Owner:     
      Type:  defect        |           Status:  new
  Priority:  major         |        Milestone:     
 Component:  Unclassified  |         Keywords:     
 Sensitive:  0             |   Estimatedhours:  0  
     Hours:  0             |         Billable:  1  
Totalhours:  0             |         Internal:  0  
---------------------------+------------------------------------------------
 Copied the comments from #299:

 {{{
 First of all, are we intentionally allowing multiple clients to connect to
 the xfrout server via the unix domain socket? The current implementation
 allows that because it inherits from ThreadingUnixStreamServer. This
 behavior might be good (e.g. if we use a multi-process model for b10-auth
 in the future, each sub process may want to make a separate connection to
 xfrout), but I'm not sure about the intent from the code. Actually, it
 rather seems to assume a single client.

 Second, since the actual xfrout session works in the blocking mode, we
 cannot handle multiple xfrout sessions concurrently. This is not good if
 we have multiple large zones and when xfrout sessions run for these zones
 at the same time. And, of course, the shutdown procedure cannot (always)
 be as quick as it should be.

 Depending on the answer to the first point, we might rather avoid using
 the socketserver framework. And, for the second part we need more
 sophisticated operation for xfrout sessions.
 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/407>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development