MobileRead Forums - View Single Post

eureka · 05-28-2012, 05:56 PM

lipc-daemon isn't the daemon that serves all LIPC communication. It's a wrong assumption. LIPC is a thin abstraction on top of D-Bus. And lipc-daemon uses this abstraction and only exposes properties as com.lab126.system publisher. So it's OK that other publishers are still accessible when lipc-daemon is stopped.

05-28-2012, 05:56 PM	#12
eureka but forgot what it's like Posts: 741 Karma: 2345678 Join Date: Dec 2011 Location: north (by northwest) Device: Kindle Touch	lipc-daemon isn't the daemon that serves all LIPC communication. It's a wrong assumption. LIPC is a thin abstraction on top of D-Bus. And lipc-daemon uses this abstraction and only exposes properties as com.lab126.system publisher. So it's OK that other publishers are still accessible when lipc-daemon is stopped.