Hi,
On Tue, 2014-01-14 at 13:47 +0100, Daniel Wagner wrote:
> When a service is created it wont be announced that it exist via
> service_state_changed(), there is create state event. The same goes
> for the removal.
Why does session care about each individual service? When a session
issues a Connect(), service autoconnect is run. Service autoconnect
already works so that it selects one service per bearer type and
connects them in parallel. The end result is that the session code gets
information on connected services only, not the rest that are of no
interest to it. For this the normal service notifier is enough. There is
no way any useful information is provided by tracking all services when
they are added until they are removed, as all the session code does is
asking the service code to try to autoconnect them.
> There is no way to know when a services was added or removed as it is.
> auto_connect_service() asks session.c to give the current list of
> services which are allowed (passed the filtering rules, which are
> currently the AllowedBearers but as I indicated, I need it also as per
> service name).
If they are needed by service name, then surely the name must be stored
somewhere, right? In that case the upcoming code could actually hand
over also a service name, not just service types.
Cheers,
Patrik
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
