From: Daniel Wagner <[email protected]>
Remove this setting from the D-Bus API and move to the configuration
plugin.
---
doc/session-api.txt | 30 ------------------------------
1 file changed, 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
etc.
- 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.
--
1.7.12.rc1.16.g05a20c8
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
