D-Bus allows programs to communicate. How is this IPC implemented? Unix domain sockets, shared memory + semaphores, named pipes, something else? Maybe a combination?
This is very similar to the DBus query question. And the answer from Googling was sockets - for TCP / IP or Unix Domain.
I think it usually uses UNIX sockets. On Linux, it can use Unix sockets for an abstract namespace that are the same, except that they do not physically exist as visible files in the file system.
Apparently IPC or TCP / IP:http://www.freedesktop.org/wiki/Software/dbusUpdate:I mean several IPC methods for different operating systems, as well as TCP / IP.http://dbus.freedesktop.org/doc/dbus-daemon.1.html shows that the unix reference edition uses both unix domain sockets and tcp / ip.
There in the past I tried to use netlink sockets directly from the kernel. More recently (announced during the last LPC), some people are working to get rid of the D-Bus user space daemons and put the D-Bus in the kernel, they will probably also use sockets, but they may revive netlink or other approaches.