Age | Commit message (Collapse) | Author | Files | Lines |
|
Fixes BMC#25978
|
|
|
|
|
|
|
|
The AvoidHandover boolean was there to fine tune the selection
algorithm in ConnMan. It was never implemented. Let's get rid
for the time beeing. If there is a real need for it we should
implemented this setting through the configuration plugin.
|
|
Reorder and group the settings, first the read only values
and then the ones which can be changed.
|
|
Remove this setting from the D-Bus API and move to the configuration
plugin.
|
|
The EmergencyCall setting which should be set by the platform integrator
and not by the application developer is moved the configuration plugin.
|
|
This setting is implicitly already available through AutoConnect.
Having yet another way to express this doesn't make it work any better.
|
|
Remove this setting from the D-Bus API and move it to the
configuration plugin.
|
|
SO_MARK can only be set if the application has the CAP_NET_ADMIN
capability. We don't want to give that to all application for
good reasons and thus this approach won't work. Also touching all
applications to get this feature working is not a good idea. We
are going to use a cgroup controller to set SO_MARK and therefore
we don't need it in the Session API.
|
|
The idea was to let ConnMan know and optimize the connection
scheduling. Doing this per Session is a bit over-engineered.
The only use cases that have come up so far was for things like an
email client checking for new message.
Past experience showed that this kind of interface lead easily to
live locks. If there is need for such a feature, doing it on a per
technology would make more sense. For the time beeing it will be
removed. Later it could still be added to the Technology API.
If an application still wants to have a connection on regular
basis it can call the Session Connnect() method. ConnMan is still
able to defer any connection request.
|
|
The ConnectionType configuration option will be moved to
the config plugin when we know how the application can be
uniquely identified in a persistent way.
|
|
Having an IdleTimeout per Session is not really reasonable. It is
hard to define the right behavoir if the timeouts differ per Session.
Doing this per technology is easier to understand and also makes
sense when no Session is used.
IdleTimeout is only documented here, it's not yet implemented.
|
|
|
|
|
|
|
|
|
|
|
|
Also change the meaning of the flag, back to the original proposal
from Marcel Holtmann.
|
|
Allowed are RoamingPolicy "default", "always", "forbidden", "national"
and "international"
|
|
|