BIND 10 #2934: xfrout session can be broken due to EAGAIN

[BIND 10 Development]

#2934: xfrout session can be broken due to EAGAIN
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  xfrout        |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:2 vorner]:
 > Yes, this really helped with my problem. It wouldn't cross my mind it
 could be this.
 >
 > Should we just merge such a small patch? Or do we need the full review
 overhead for these 4 lines?

 We'll at least need a test.  I also wonder whether we might rather do
 asynchronous write, because otherwise an evil or hangup client could
 hold the session unnecessarily long.  With blocking write we cannot be
 responsive to shutdown event either.  It may be okay to defer these
 things to the planned complete rewrite, but I think we should at least
 discuss them here.

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