BIND 10 #366: The socket creator process
BIND 10 Development
do-not-reply at isc.org
Thu Apr 7 08:34:23 UTC 2011
#366: The socket creator process
-------------------------------------+-------------------------------------
Reporter: vorner | Owner: vorner
Type: | Status: reviewing
enhancement | Milestone:
Priority: major | Sprint-20110419
Component: | Resolution:
Unclassified | Sensitive: 0
Keywords: | Add Hours to Ticket: 0
Estimated Number of Hours: 0.0 | Total Hours: 0
Billable?: 1 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => vorner
Comment:
Replying to [comment:8 vorner]:
>
> > It would seem the README could use a little bit more info on exactly
what is sent back on success (and when).
>
> I'm not sure I understand what you mean. I added something about how the
socket is sent. But what do you men by when? It's just sent right away,
why would it wait for anything?
>
n/m; Somehow I initially read that part as 'then the socket is sent with
send_fd() *over another channel*. Maybe I'm the only one, if not, making
the sentence 'The answer to this is either 'S', followed by' might be a
tad bit better, but your call, the current text is fine. I think the empty
send_fd() function that was there might have thrown me off.
--
Ticket URL: <http://bind10.isc.org/ticket/366#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list