From: Daniel Wagner <[email protected]>
Having an IdleTimeout per Session is not really reasonable. It is
hard to define the right behavoir if the timeouts differ per Session.
Doing this per technology is easier to understand and does also
make sense when no Session is used.
---
doc/session-api.txt | 9 ---------
doc/technology-api.txt | 8 ++++++++
2 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/doc/session-api.txt b/doc/session-api.txt
index e19c6bf..90002ba 100644
--- a/doc/session-api.txt
+++ b/doc/session-api.txt
@@ -241,15 +241,6 @@ Settings string Bearer [readonly]
settings becomes available becomes available. Using
this feature it is also easy to avoid congestion.
- uint32 IdleTimeout [readwrite]
-
- If the system is idle for given period then it should
- go offline.
-
- If the timeout is 0, this feature is disabled. If
- different values are provided by several session object
- the longest interval is taken as timeout value.
-
boolean EmergencyCall [readwrite]
Boolean representing the emergency mode of the
diff --git a/doc/technology-api.txt b/doc/technology-api.txt
index 6429776..f90343c 100644
--- a/doc/technology-api.txt
+++ b/doc/technology-api.txt
@@ -93,3 +93,11 @@ Properties boolean Powered [readwrite]
This property is only valid for the WiFi technology,
and is then mapped to the WPA pre-shared key clients
will have to use in order to establish a connection.
+
+ uint32 IdleTimeout [readwrite]
+
+ If the technology is idle for given period then it
+ will go offline if no Service with this technology
+ has AutoConnect set to True.
+
+ If the timeout is 0, this feature is disabled.
--
1.7.12.rc1.16.g05a20c8
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
