Native Service vs Native Daemon

1,295 views
Skip to first unread message

ramakrishna k

unread,
Sep 28, 2011, 12:49:00 PM9/28/11
to android-...@googlegroups.com
Hi All,

can any one tell me the difference between Native Service and Native Daemon?
Why framework deals with the sockets to interact with Native Daemon(ex:rild) where as with Binder IPC for Native Service?

and also

what is the difference between D-bus and Binder IPC and why framework uses D-bus to interact with BlueZ bluetooth library?

thanks
siva ramakrishna

penguin359

unread,
Sep 28, 2011, 7:16:46 PM9/28/11
to android-...@googlegroups.com
Daemon, D-Bus, and Domain Sockets refer to UNIX/Linux Technologies that power the underlying Operating System.  These same technologies are also use on other Non-Android Linux systems such as Ubuntu Linux Desktop.  Binder IPC and Services more refer to technologies used in Android that runs on top of Linux.  Bluez is the Bluetooth library used on any Linux system and you talk to it using D-Bus.  Google deemed D-Bus and Domain Sockets (which are the standard type of IPC used in Linux) as too heavy weight to run a whole bunch of Android Apps talking to each other and created the Binder IPC as a lightweight IPC.  Binder IPC is patched into the Linux Kernel, designed for fast, lightweight communications and only exists on Android Devices at this time.

Drunczyk

unread,
Oct 1, 2011, 10:57:05 AM10/1/11
to android-...@googlegroups.com
How to use the Binder IPC if I write a daemon and an APK and want them to communicate to each other?

Dr
Reply all
Reply to author
Forward
0 new messages