On 11/12/2013 11:15 AM, Chengyi Zhao wrote:
2013/11/11 Daniel Wagner <[email protected] <mailto:[email protected]>>

    On 11/10/2013 10:47 AM, Chengyi Zhao wrote:

        Hi Daniel,


        2013/11/8 Daniel Wagner <[email protected].__de 
<mailto:[email protected]>>

            From: Daniel Wagner <[email protected] 
<mailto:[email protected]>>

            When SessionAutoConnectMode is enabled we should also make sure
            we disconnect unused Services. Unused means there is no
            Session is using a Service (__connman_session_in_use()) and
            asking for a connection (__connman_session_wants___connection())


        IMHO, if SessionAutoConnectMode is enabled, when service is created 
session
        should  be created,


    SessionAutoConnectMode is a configuration flag which doesn't change during
    runtime. It changes the way AutoConnect is interpreted. I don't follow
    you here: why should a new Service be created when a Session should also
    be created? Could you please elaborate?


By default, I think the application does not need to create session, so connman 
should automatically manager
the session.

That is supported. There is no need to have a Session. As I pointed out
you can use Session or Service together or alone. The only thing
which SessionAutoConnectMode is changing is how the AutoConnect
is interpreted.

In other words, even if the application does not use a session, also able to 
use the default networkpolicy.

Don't worry, this is supported since day one :)

cheers,
daniel



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

Reply via email to