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

[Michal 'vorner' Vaner]

Hello

On Tue, Mar 12, 2013 at 12:26:13AM -0700, JINMEI Tatuya / 神明達哉 wrote:
> So are you intending to use a (separate?) CC session directly, instead
> of the module CC session API?  (The latter currently doesn't provide
> information like "l-name").  Also, how can a module (in practice, a
> "consumer") knows if the sender is the manager or a consumer?  lname
> doesn't have that information, so, without some extension, I suspect a
> module cannot determine when it's notified of a departure of some
> other module on the "channel" whether it's the manager (so it may have
> to do something) or other consumer (in which case a mere consume can
> simply ignore it).

Digging through the code, I didn't notice the module session doesn't provide the
headers of message. I though the groupRecvMsg did provide them, it seems the
command handler does not, which looks like an oversight. Anyway, notification
callbacks could have the headers passed, so you could get the lname from them.

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.

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/20130312/0c602516/attachment-0001.bin>