[bind10-dev] take 2: design and inter-process protocol for shared memory

[Michal 'vorner' Vaner]

Hello

On Thu, Mar 14, 2013 at 11:48:34AM -0700, JINMEI Tatuya / 神明達哉 wrote:
> >    Also, for simplicity, I think we should just be sending the ACK every time.
> >    Omitting it on startup won't give us any benefit and it'll be some additional
> >    handling.
> 
> Regarding the latter part, that's one option.  I thought it's useful
> for the manager if it can determine whether an ack is really expected
> or a kind of error (sent by someone not requested).

I don't really understand the goal here. It is to detect when someone completely
unrelated sends an ACK? Why? I mean:
 • How could that reasonably happen? (even more if it was just the reply to the
   command, the sender would have to know the seq of the command, so it couldn't
   be completely unrelated ‒ the chance of someone just hitting the same seq is
   quite low.
 • What would we do when we detected that? Is there any reasonable way how to
   handle such situation?

I guess I didn't understand the intention correctly, since what I understand
doesn't seem to make much sense to me.

With regards

-- 
When eating an elephant take one bite at a time.
		-- Gen. C. Abrams

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/20130315/caabd324/attachment.bin>