Re: Note about device activation in current trunk...

["Tambet Ingo" <tambet gmail com>]

On 10/1/07, Helmut Schaa <hschaa suse de> wrote:
> Am Montag, 1. Oktober 2007 08:02:18 schrieb Tambet Ingo:
> > On 9/29/07, Helmut Schaa <hschaa suse de> 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?

<node name="/">
  <interface name="org.freedesktop.NetworkManager">

    <method name="ActivateDevice">
      <annotation name="org.freedesktop.DBus.GLib.Async" value=""/>
      <arg name="device" type="o" direction="in"/>
      <arg name="service_name" type="s" direction="in"/>
      <arg name="connection" type="o" direction="in"/>
      <arg name="specific_object" type="o" direction="in"/>
    </method>
....
</node>

Note that the call is supposed to be asynchronous: It will not return
before it knows the device activation will be started. If the
connection referenced by "connection" object path is not found, NM
waits for up to 5 seconds in hope to receive the connection. If the
call is made synchronously (from a single threaded app, that is),
there is no way NM would be able to update it's known connections from
the frontend (which is blocking on waiting for the reply).

Tambet