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

[Michael Graff]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2010-05-16 11:53 PM, Shane Kerr wrote:

> BUT... if we assume reasonable zone refresh rates and/or relatively
> decent connectivity, then this won't be such a big problem. Consider
> that with 100k zones and a 2-hour refresh rate, we should see only a few
> 10s (20? 30?) of transfers in progress during normal operation. Someone
> with 100k zones won't be surprised to see lots of processes! ;)

Wait, I thought xfer-in was called only when there was something to
transfer, not for a SOA check or simple refresh operation.

> So I think it is not always possible to limit the number of XFR in
> progress to a "reasonable" number. So I think a threaded (or
> event-driven) model makes sense here.

I will still throw in for the "keep it simple, make it complicated
later" approach of single threaded design and implementation.

> The XFR code is relatively simple now, and if it remains simple we can
> be more sure that it is robust. I propose we go forward with the
> threaded model until we discover that it is broken, and then fix it if
> necessary.

I propose the opposite, for the very same reasons:  the code is simple,
keep it simple until there is a reason to complicate it.

- --Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvxY94ACgkQ+NNi0s9NRJ2p4gCfYAoN9J0Nx6Ja6LwwTLzKnoaB
NWMAn0k33Mw9IrvMWsRGolZk9SYkBzEe
=GbYZ
-----END PGP SIGNATURE-----