[bind10-dev] Thoughts on Architecture of Xfrin & Notify-In/Out

[zhanglikun]

Reply to Jinmei’s comments in 5.13’s call meeting.

> Jinmei: Assuming we handle notify in the auth serv process, the zone 
> manager
> doesn't have to handle handle message format. So it will be simpler and 
> safer.
> Also we can kill any xfr in process if a particular transaction goes wrong 
> while
> keeping zone manager processing. I didn't think about other details, but
> separating these two tasks seems to make more sense.

Yeah, make sense to separate zone manager and xfrin as two processes. When 
xfrin crash or is killed, zone manager is still running, so we don't need to 
restart the zone-maintenance timer from beginning.

> Jinmei: There are two possibilities: one for zone management and one for 
> xfr,
> where the xfr has multiple threads. Or we have one zone management and one
> per transfer, so many xfr processes. I didn't have a particular idea about 
> these
> two choices. What I mainly focused on is having a single process to do
> everything.

I preper to one process for zone manager, one process for xfrin.  Xfrin will 
has multiple threads, one thread for one transfer, and xfrin should maintain 
one transfer-task queue if there is too many concurrent transfer tasks (more 
than max_transfer_in)needs to be done.

Zhang Likun