BIND 10 #151: XfroutClient socket location and removal

[BIND 10 Development]

#151: XfroutClient socket location and removal
--------------------------+-------------------------------------------------
 Reporter:  jreed         |        Owner:  zhanglikun
     Type:  defect        |       Status:  assigned  
 Priority:  major         |    Milestone:            
Component:  Unclassified  |   Resolution:            
 Keywords:                |    Sensitive:  0         
--------------------------+-------------------------------------------------
Changes (by jinmei):

  * owner:  jreed => zhanglikun


Comment:

 Replying to [comment:3 zhanglikun]:
 > You can commit it temply, But sometime it doesn't work, I am working on
 a new patch for it.

 Thanks for checking.  But now that you've looked at it: I was feeling this
 might be done within the !ThreadingUnixStreamServer class.  A
 !ThreadingUnixStreamServer object creats the file for communication on
 creation of itself, so it seems to me more natural that the file is
 removed on destroying the object.  It just doesn't look intuitive we need
 to remove the file explicitly outside the class.  Wouldn't there be a more
 natural way to handle this?

-- 
Ticket URL: <https://bind10.isc.org/ticket/151#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development