Hi David,
On Thu, Mar 1, 2012 at 10:44 PM, David Miller [off-list ref] wrote:
From: Eric Dumazet <redacted>
Date: Thu, 01 Mar 2012 04:26:42 -0800
quoted
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, ...).
I actually don't understand why there is so much resistence to using a
real bonafide on-the-wire protocol, and that way if you ever wanted to
connect dbus instances on multiple machines or log dbus transactions
remotely for debugging, you could just do it.
I don't think you understood the problem, we want something that scale
for less powerful devices, why do you think Android have all the
trouble to create binder?
Besides what is really the point in having AF_UNIX if you can't use
for what it is for?
"The AF_UNIX (also known as AF_LOCAL) socket family is used to
communicate between processes on the same machine efficiently."
--
Luiz Augusto von Dentz