quoted

So, now we are trying a different approach. To create a new address
family AF_MCAST. That way we can have more control over the

semantics of

quoted

the socket interface for that family.

We expect to have some patches in a few days and we will resend.

Does this makes more sense to you?

Why adding an obscure set of IPC mechanism in network tree, and not
using (maybe extending) traditional IPC (Messages queues, semaphores,
Shared memory, pipes, futexes, ...).

If it isn't a totally silly suggestion, why not write a simple
device driver that just does what you want?
Which (I think) is named pipes with multiple readers.

	David