[bind10-dev] proposal: revising listen port configuration

[Michal 'vorner' Vaner]

Hello

On Tue, Apr 03, 2012 at 11:15:09AM -0700, JINMEI Tatuya / 神明達哉 wrote:
> ...we should consider the case where the acquisition of new socket
> fails after the server responds to the config update.

Do we really? I mean, it kind of makes sense to be able to respond to a command
asynchronously as well. So the workflow would look like:
 • We got a config update.
 • So we send out bunch of requests for the new sockets, with a callback.
 • We return, but don't send the answer yet.
 • Sometime later, the callback(s) is(are) called. We change the sockets and
   send the answer.

But I'm not sure if it's really worth it.

Anyway, I'd very like to be able to decouple the config validation from config
update operations, for several reasons. Now, with multiple instances of
components, each of them validates. If they don't agree on the validity, race
conditions happen and the fastest to answer wins. Handling of local and remote
config is different. And we have no way to validate config if the component is
not running.

If the validation was taken out of the process and placed somewhere else, the
config update would be just a notification and there would be no answer to it
anyway.

With regards

-- 
Next sleep is scheduled after 1k lines of code

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20120404/76c3e5dc/attachment.bin>