Hi Patrik, On 01/15/2014 12:13 PM, Patrik Flykt wrote: > On Wed, 2014-01-15 at 09:41 +0100, Daniel Wagner wrote: >> I don't see how this would help currently because AUTO and SESSION is >> essentially the same. auto_connect_service() does not care who has >> asked for a connection. > > Then we need to provide that information to auto_connect_service().
I see, I'll try that. >>> With that there would not be any reason to add this kind of >>> disconnect functionality run once in a while. >> >> We need to run the auto connect algorithm any time the configuration >> of a session changes. It is far from random or 'once in a while'. > > Auto _disconnect_ should happen immediately after the last session using > the service calls Close(). There's no need for any hangarounds waiting > to be detected by auto_disconnect_service(). And that is what is happening, obviously it is possible to optimize the all session gone use case. IIRC we discussed the benefits of having a __connman_auto_disconnect() and we agreed that it is not brilliant idea. Instead it would be better when the auto connect part handles this. cheers, daniel _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
