Hi Patrik, On 10/18/2011 08:52 AM, Patrik Flykt wrote: > On Mon, 2011-10-17 at 09:07 -0700, Marcel Holtmann wrote: >> This was added to give installers a simple way of finding the service >> object for a given network interface. > > The problem is/was twofold. First of all given the network interface > name, code for finding out the service based on it was sent to the > mailing list only last week. > > The other part of the problem still exists: the current documentation > specifies that if there are more than one matching service, an error is > returned. There was a lengthy discussion in last week's bug scrub > meeting about whether it'd be ok to return the service which is > currently connected instead. This was seen as inconsistent behaviour and > as looking up 'wlan0' would in practise always return an error and not a > service, the whole function was deemed impractical and subject for > removal. > > I don't have any strong opinions either way. In order to keep the > current functionality documentation really should change if there is > going to be any practical applications of looking up services by their > interface names. I'd also be curious to know whether anyone has been > using the functionality, especially since matching interface names has > been missing for this long. Service matching can also be done in the > clients, as they can get a list of all services from the manager api.
I think we need this feature for the Session API. IIRC, we had during a face to face meeting a lengthy discussion why there shouldn't be a Strength setting in the Session API. The main argument was that if we really want to know this information we should use Manager.LookupService() and read the signal strength from there. The Session API has the proper name, so LookupService should always only find one matching Service. cheers, daniel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
