How to use dbus as the IPC sync method in different IPC namespace

[Simon McVittie]

On Thu, 22 Dec 2011 at 10:52:32 +0800, yinxb wrote:
>    I have an App running  in its own IPC name space for isolation purpose,
>    and now I need to do IPC sync with App(which is known as UX)
> running in another IPC namespace  for UI display sync.

If D-Bus still works in this situation, you could argue that this is a serious
bug in your IPC namespacing :-)

D-Bus normally uses abstract Unix sockets (on platforms that support them -
Linux and possibly others), normal path-based Unix sockets (on other Unix
platforms), or TCP sockets (on Windows, but it's possible to do so on Unix
too). If your IPC namespacing prevents these from working, D-Bus won't work;
if your IPC namespacing does not prevent these, then D-Bus can be made to
work.

You will need to use a hard-coded ("well-known") socket address for your bus,
or communicate the dynamic bus address from one app to the other somehow.

    S