From: Daniel Wagner <[email protected]>

---
 doc/session-overview.txt |   23 +++++++++++++++++++++++
 1 files changed, 23 insertions(+), 0 deletions(-)

diff --git a/doc/session-overview.txt b/doc/session-overview.txt
index 65cbcc2..10852c6 100644
--- a/doc/session-overview.txt
+++ b/doc/session-overview.txt
@@ -133,3 +133,26 @@ the data.
 The configuration plugin is also able to constrain and enforce the
 settings. For example the roaming policy can only be changed by
 trusted application.
+
+
+Additional Information on Settings
+==================================
+
+PeriodicConnect and IdleTimeout
+-------------------------------
+
+If an application wants to go online periodically (e.g. checking for
+new mails) then the application should use PeriodicConnect instead of
+calling Session.Connect() periodically. There is no need for the
+application to maintain timers. ConnMan is also able to try to combine
+several PeriodicConnect calls into one. Applications should not rely on a
+very precise periodic connect. Apart of merging periodic connect
+timeouts there is also the problme that no service might be available
+at that point and ConnMan will defer the connect call.
+
+The IdleTimeout tells ConnMan when a link is idle for given eriod it
+is okay to disonnect.
+
+PeriodicConnect and IdleTimeout should only consired as hints. ConnMan
+will try to meet them but there is no garantee for doing so. For
+example global settings have precedence of session settings.
-- 
1.7.4.4

_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman

Reply via email to