BIND 10 #216: Xfrin: Implement the feature items in TODO file.
BIND 10 Development
do-not-reply at isc.org
Tue Oct 12 09:38:03 UTC 2010
#216: Xfrin: Implement the feature items in TODO file.
------------------------------+---------------------------------------------
Reporter: zhanglikun | Owner: shentingting
Type: enhancement | Status: reviewing
Priority: major | Milestone: y2 6 month milestone
Component: xfrin | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: 0.0 | Hours: 0
Billable: 1 | Totalhours: 5.0
Internal: 0 |
------------------------------+---------------------------------------------
Comment(by shentingting):
>> http://bind10.isc.org/ticket/216?replyto=29#comment:17
> I saw your changes, and I agree with you.
>> http://bind10.isc.org/ticket/216?replyto=29#comment:19
>>isn't it better to delete completed threads as soon as possible? in the
current implementation they are not purged until a new xfrin attempt
occurs.
> For this, We can delete completed threads as soon as possible. but when
we delete completed threads, it will find this thread`s fd in hash map,
this waste time. I purged it when a new xfrin attempt occurs. This will
not run delete, it save time. Although It will occupy some memory, but It
is little, it`s number less than max_transfers_in. So I did so.
>>I believe we should use select for connect and send while watching a
shutdown event. consider, e.g., the case where a shutdown event is sent
when the primary server is dead and connect blocks. but it's okay for me
to leave this enhancement to another ticket (or we should rather do so)
> I think it is better to create another ticket to solve this.
> For the newest code, I delete connect function. For error code 0, it is
success, so there is no exception, And add a DEFAULT_TRANSFER_IN variable
to remove the hardcoding.
--
Ticket URL: <http://bind10.isc.org/ticket/216#comment:31>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list