Am Montag, 1. Oktober 2007 08:02:18 schrieb Tambet Ingo: > On 9/29/07, Helmut Schaa <[EMAIL PROTECTED]> wrote: > > ActivateDevice would then take the device's object-path and the > > connection's object-path as arguments, right? > > Internally, yes, but it will not be exposed over dbus.
So, how would the call look like? > > Not sure about this. The interface would be much more obvious if > > Activate would stay as a device-method. > > Not really. Devices don't have any stored connections you reference by > path and service_name argument, NMManager has. It would make just as > much sense as NMConnection.Activate(o device_path) than the other way > around. Since the manager keeps track of devices and connections and > thus ties them together, it's the obvious place for the activation. Agreed. Sounds reasonable :) > The reason why it was NMDevice.Activate(connection) was that it used > to make sense when the whole connection was sent to the device with > activation request. The problem was, that would not work with "system" > connections (pre-configured by system administrator) where only the > connection path is available for the user activating the connection. Regards, Helmut _______________________________________________ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list