path: root/doc
diff options
authorDaniel Wagner <>2012-08-13 08:40:24 (GMT)
committerPatrik Flykt <>2012-08-30 10:02:19 (GMT)
commit9844cb3d499b654e6d337dab29673513680b6bb5 (patch)
treed266fa31e7d01865976f63fead9cc74a509f5a85 /doc
parentc7cd2709d524d8e5d7ee2f6ec1eff2166b4f1239 (diff)
session: Remove Priority documentation
Remove this setting from the D-Bus API and move it to the configuration plugin.
Diffstat (limited to 'doc')
1 files changed, 0 insertions, 30 deletions
diff --git a/doc/session-api.txt b/doc/session-api.txt
index 3d907a0..252a904 100644
--- a/doc/session-api.txt
+++ b/doc/session-api.txt
@@ -131,36 +131,6 @@ Settings string Bearer [readonly]
is done to avoid congestion on bearers like cellular
- boolean Priority [readwrite]
- This allows a session to mark itself as priority or
- not. In general application are not allowed to make
- themselves more important than others.
- The priority handling is done internally by usage
- and first come, first serve order. By default this
- settings is of course false.
- Internally there can be different priorities for
- different application, but these are defined by a
- configuration file and not via this interface.
- An application that calls the method to connect
- a session is preferred over other sessions. This
- priority value is more for application that want to
- push themselves up in the asychronization notification
- queue once a bearer becomes online.
- This actual priority order also depends on the
- allowed bearers and other factors. This is setting
- is just a little indicator of one application being
- notified before another one.
- For example a streaming session should set the
- priority value. As soon as realtime data is involved
- then this should be set. An email client should not
- set this value.
string Name [readonly]
The Service name to which the system is connected.