New wpa_supplicand dbus API proposal

[Dan Williams]

On Tue, 2009-06-16 at 23:16 +0200, Marcel Holtmann wrote:
> Hi Dan,
> 
> > > > O:
> > > > /fi/w1.wpa_supplicant1/Interfaces/<interface_number>/Networks/<network_number>
> > > > I: fi.w1.wpa_supplicant1.Interface.Network
> > > > 
> > > > P: Enabled (read/write) -> b
> > > > P: <wpa_supplicant network block properties> (read/write) -> a{sv}
> > > >      - Most properties can be set as strings, but can also be set
> > > >        as a byte array if necessary (SSID, BSSID, PSK, etc).  Supplicant
> > > >        can autoconvert like it does right now.
> > > > 
> > > > S: PropertiesChanged -> a{sv}
> > > 
> > > So what is the difference between Enabled and SelectNetwork() call. This
> > > differentiation confused the hell out of me already with the current
> > > code. Why do we bother here at all.
> > > 
> > > Lets just use SelectNetwork() to switch between networks and forget
> > > about Enabled stuff. If some network should not be in the list, then
> > > just lets use RemoveNetwork().
> > 
> > If we were to just use SelectNetwork(), how would we completely
> > disconnect the supplicant and tell it to stop doing anything?  We could
> > make SelectNetwork with a blank object path do that for us.
> 
> yeah and that is not gonna work out. D-Bus doesn't allow an empty object
> path.

Sorry, I really meant "/" not blank.

> > BTW, enabled/disabled is what allows the supplicant to make the roaming
> > decisions for us, so while it doesn't get used by NM right *now*, maybe
> > we want to push that sort of thing to the supplicant in the future.
> > Currently NM only enables one network at a time.
> 
> So personally I think every network we add is part of our roaming
> agreement. If we don't want it anymore, we have to remove the network
> again. That way we keep it simple.
> 
> Maybe we should not have a SelectNetwork at all. Just add/remove
> networks and then have a global on/off switch on the Interface
> interface.

That's fine by me.

Dan