Le jeudi 01 mars 2012 à 12:57 +0100, Javier Martinez Canillas a écrit :

Yes, you are right it doesn't follow AF_UNIX semantics so Unix sockets
is not the best place to add our multicast implementation.

Right, AF_UNIX is already a nightmare to maintain.

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
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, ...).