Changeset 5f3243f in Dbus API specifications

Timestamp:

02/04/09 08:37:36 (4 years ago)

Author:

Michael 'Mickey' Lauer <mickey@…>

Branches:

820cacfd324a623a04b3e22f319e9220819d6ec4, 0.11, 675acad2f1510526a93c9777d03664766c823aab, morphis/pending, morphis/sms-rework

Children:

262afc1

Parents:

140fda8

git-author:

Michael 'Mickey' Lauer <mickey@…> (02/04/09 08:37:36)

git-committer:

Michael 'Mickey' Lauer <mickey@…> (02/04/09 08:37:36)

Message:

usage: document resource policy handling

File:

• html/usage-intro.html (modified) (1 diff)

html/usage-intro.html

@@ -103 +103 @@
   Once a client starts up again, it has to treat all resources as being released and need to request them again.
 </p>
+<p>
+  Note that the automatic release behaviour especially affects dbus command line tools such as <b>dbus-send</b> or <b>mdbus</b>, which usually only stay on the bus for very short periods. If a client can not stay on the bus while it wants to access a resource, you need to resort to the policy interface (see next section).
+</p>
 
 <h1>Resource Policies</h1>
 <p>
-  ... when and how to use the policy interface
+  Once in a while, reference counted handling of resources gets in your way, for example when you are running legacy applications or want to configure or debug peripherals. In that case it may become necessary for a resource to be always enabled or always disabled. While not recommended, it is possible to switch from automatic resource control to manual control by calling <a href="http://docs.freesmartphone.org/org.freesmartphone.Usage.html#SetResourcePolicy"><tt>SetResourcePolicy</tt></a>.
+  Valid values are <b>auto</b> (which is the default on system startup), <b>enabled</b>, and <b>disabled</b>.
 </p>