BIND 10 #1542: socket creator protocol should distinguish socket level and other errors

[BIND 10 Development]

#1542: socket creator protocol should distinguish socket level and other errors
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20120207
                   Priority:         |            Resolution:
  blocker                            |             Sensitive:  0
                  Component:  Boss   |           Sub-Project:  DNS
  of BIND                            |  Estimated Difficulty:  4
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
  Socket creator                     |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => UnAssigned
 * status:  accepted => reviewing


Comment:

 I used exceptions (because it is easier to code, can contain more
 information and the code using it doesn't need to be changed (yet) to
 reflect the change). I derived a NonFatalSocketErorr (and used it as a
 base for two other exceptions, so the user of the function can have more
 details if he wants so) from the SocketError.

 Should the code using it do something special now? Because currently it
 just rejects the configuration, no matter which error it is.

 I'd propose this as a changelog entry:
 {{{
 [func]          vorner
 The SocketRequestor provides more information about what error happened
 when
 it throws, by using subclasses of the original exception. This way a user
 not interested in the difference can still use the original exception,
 while
 it can be recognized if necessary.
 }}}

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