clarity of concept
clarity of concept
Posted Nov 13, 2014 21:16 UTC (Thu) by oak (guest, #2786)In reply to: clarity of concept by mezcalero
Parent article: Kdbus meets linux-kernel
DBUS had already in the beginning (decade ago) couple of other important philosophical differences from doing C-code (or using CORBA):
* CORBA calls are by default synchronous, like function calls, but DBUS calls are by default asynchronous. If you don't expect reply, but are just notifying something, messages are fire & forget
* Message recipients don't need to exist before being called, DBUS daemon can "auto-activate" them when messages are sent to them
* CORBA calls are by default synchronous, like function calls, but DBUS calls are by default asynchronous. If you don't expect reply, but are just notifying something, messages are fire & forget
* Message recipients don't need to exist before being called, DBUS daemon can "auto-activate" them when messages are sent to them