On Tue, 2012-10-09 at 15:44 +0200, Marcel Holtmann wrote:
> however the
> description in the main.conf is bad. That needs at least work.
That's fixable for sure :-)
> And the one important question is that if this means READY connections
> or ONLINE connections. For example if you have a working ONLINE
> connection in single mode and you already switch at READY, then you
> might end up with no Internet connectivity at all.
>
> Has this been really thought through? Or are we hacking around for a
> customer here?
When a user decides to connect a service, that service needs to become
connected independent of what other services there are at the moment.
For a normal case with PreferredTechnologies set this works fine even if
the new service might not get the default route.
In case of a single connection policy, the user connected service needs
to be able to evict any other service on the system. This includes
replacing an 'online' service with 'ready' one. If not, then the user
interaction will become most interesting.
In order to keep the complexity down on the first iteration of this
policy for the mailing list, I decided to keep it as simple as possible
and always keep the last connected service. It should be almost trivial
to modify the behavior so that a single connection policy with preferred
technologies set would not choose a 'ready' technology over an 'online'
one. But a user connected one still needs to take precedence, or else we
have services that never seem to be connectable.
I'll do a new iteration of the SingleConnection policy with the 'online'
state in mind. Thanks for the feedback!
Patrik
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
