[bind10-dev] Resend: Re: proposed system design and inter-process protocol for shared memory

[JINMEI Tatuya / 神明達哉]

At Tue, 12 Mar 2013 08:50:36 +0100,
Michal 'vorner' Vaner <michal.vaner at nic.cz> wrote:

> And distinguishing that would be actually simple. The unsubscription
> notification would be for a connection leaving a group. And the manager would be
> subscribed to the MemMgr group (or whatever it would be called) as the only one,
> while consumers to MemMgrConsumer.

So the notification thing will work as follows?

1. memmgr subscribes to the MemMgr group (as we currently do)
2. others subscribes to the MemMgrConsumer or whatever group (as we
   currently do)
3. memmgr requests msgq to notify it of any updates on the membership
   of the MemMgrConsumer group
4. others request msgq to notify them of any updates on the membership
   of the MemMgr group (in this case the only possible change is
   actually a departure (and startup?) of memmgr)

If so, does step 3 work if step 2 isn't completed (at least by one
"consumer") at that time?  Likewise, does step 4 work if step 1 isn't
completed at that time?  Is msgq expected to remember any outstanding
requests in case there's no subscriber of the group (so the msgq
wouldn't even know the existence of the group) at the time of the
request?

Or is this thing expected to work completely differently?

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.