1
\documentclass[a4paper, 12pt]{article}
4
pdfauthor={Antti Kaijanm\"{a}ki},
13
\title{ZinC\\Service Description Language\\---\\D-Bus Transport}
15
Antti Kaijanm\"{a}ki\\
16
\texttt{antti.kaijanmaki@canonical.com}
21
\pagenumbering{gobble}
32
\pagenumbering{arabic}
34
\subsection{D-Bus Transport}
35
D-Bus is not an object model, but it can be used to implement one.
37
As D-Bus is so relaxed on the way services and API's can be defined on top of it, object bindings for it usually turn out poorly and require per API quirks.
39
The description files can easily be mapped to dbus API's.
41
- dbus permission.conf:s generated automatically
43
\subsection{D-Bus Shortcomings}
44
way of automatically disconnect from the bus when app goes
45
to suspend a way to load the values when app comes out of suspend
47
way for the service to know when it's interface is listened to avoid unnecessary
48
loading of resources and also not keeping the service from getting wakeups on data that nobody cares for
50
\section{API Compatibility}