Hi Daniel,
On 10/10/2011 11:13 AM, Daniel Wagner wrote:
Hi,
I think an IdleTimeout per Session makes sense. It should map to a
Service and not to a bearer, BTW. If you have for example a VPN tunnel
over a cellular link and the application is only interested in idle
timeout in the tunnel.
Hmm, perhaps I am not understand the use cases well enough but this
session idle timer seems a bit over engineered solution.
Lets imagine two scenarios:
1. Each session has an idle timer which closes the session if there are
no packets sent during the session. If all the sessions are closed, the
network connection is closed also.
2. Each session has no idle timer but a global bearer specific timer is
in use. When there is no network traffic in the bearer, the bearer is
taken down (like wlan0) so all the sessions using that bearer will be
closed.
The end result is the same but the 2. is much easier to implement
(netfilter has already code for bearer specific idle timer and it was
used in maemo). Also in 2. the network connection (like wireless or
cellular one) is taken down faster which could help with power
consumption and billing.
Well, we could of course express this with a global IdleTimeout and then
only measure the traffic for the top most Service (e.g. VPN tunnel). I'm
still not convinced this is a good idea. What about PeriodicConnect
then? One could argue let's do it the same way, one global setting for
all application. The admin has just to figure it out the right value.
The Session API is there to let application configure at _runtime_.
Each app can have its own PeriodicConnect value. Connman would then just
get the smallest value and create a connect when necessary.
It would be great if we could arrange f2f mini summit to discuss complex
issues like these.
cheers,
daniel
Cheers,
Jukka
_______________________________________________
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
