Why d-bus when many IPC mechanisms are available?

[Thiago Macieira]

On quinta-feira, 23 de agosto de 2012 13.01.15, pramoda.subraya at wipro.com 
wrote:
> Hi,
> 
> Please help me to understand the d-bus by clarifying
> 
> 
> 1.    Why D-Bus when many IPC mechanisms are available?

Because none other are suitable for D-Bus's purpose: structured RPC mechanism 
with a central rendezvousing server, low-latency.

> 2.    On what IPC mechanisms, d-bus is implemented?

Sockets (Unix or TCP).

> 3.    Whats the difference bw/ d-bus and Glib or Gio ?

You're trying to compare an IPC mechanism to a generic base support library or 
a generic I/O library. It's like asking the difference between a socket and the 
C library.

> 4.    Advantages of D-bus  over other std IPC mechanisms (PIPE/Shared memory
> etc)

See above.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20120823/516d0e96/attachment.pgp>