BIND 10 #840: Windows support for libcc

BIND 10 Development do-not-reply at isc.org
Thu Apr 28 18:15:43 UTC 2011


#840: Windows support for libcc
--------------------------------------------+----------------------------
                   Reporter:  fdupont       |                 Owner:
                       Type:  defect        |                Status:  new
                   Priority:  major         |             Milestone:
                  Component:  Unclassified  |            Resolution:
                   Keywords:                |             Sensitive:  0
            Defect Severity:  N/A           |           Sub-Project:  DNS
Feature Depending on Ticket:                |  Estimated Difficulty:  0.0
        Add Hours to Ticket:  0             |           Total Hours:  0
                  Internal?:  0             |
--------------------------------------------+----------------------------

Comment (by vorner):

 I still don't understand why.

 For one, libcc does not send or receive the sockets, that's out of libcc.

 For second, send_fd can get it's own PID and send it over whatever
 comunication it has. Then the peer can read the PID, use it to get the
 socket/fd and pass out only the FD. There's no need for change of the
 interface, only of what gets over the wire. Or what I don't see?

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


More information about the bind10-tickets mailing list