Hi, > About the idle timeout I'm not sure we'd need per-session > disconnections. If the app does not want or remember to inform ConnMan > that it's usage is over, a per-bearer idle timer does the job reasonably > well. If the app in question already stopped sending/receiving data, it > wouldn't anyway drain any transmission power. Thus ConnMan would easily > just count the max of idle timeouts requested by all sessions (and its > own view on max allowable) and use that for disconnections. It's also my opinion that IdleTimeout should not be per-session. It does not sound optimized.
In Maemo, we were using IDLETIMER target on netfilter to do exactly that kind of job. See: http://kerneltrap.org/mailarchive/linux-netdev/2010/6/15/6279376/thread for more informations. The code has been accepted upstream, so there is no reason not to use it :) So such IdleTimeout should be configurable per-bearer in Manager directly, or something like that. It's imho the way to go: per-session means quite some code running per each sesssion for such timeout handling, when you can have only 1 callback waiting for sysfs notification and that's it if there is a timeout set. Hope it helps, Tomasz _______________________________________________ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
