[trunk] D-Bus (and libnm-glib) API changes today

[Dan Williams <dcbw redhat com>]

No behavioral changes, but a few things were renamed today in r2928.
They are:

Interface: org.freedesktop.NetworkManager.Device.Wireless
      * GetActiveNetworks() -> GetAccessPoints(): "Network" is really
        the wrong name here since a collection of access points defines
        a network, and NM is really dealing with access points here.  NM
        no longer coalesces access points based solely on SSID and
        therefore "network" is inappropriate.
      * ActiveNetwork property -> ActiveAccessPoint
      * NetworkAdded -> AccessPointAdded
      * NetworkRemoved -> AccessPointRemoved

libnm-glib (NMDevice80211Wireless object):
      * network-added -> access-point-added signal
      * network-removed -> access-point-removed signal
      * nm_device_802_11_wireless_get_active_network() ->
        nm_device_802_11_wireless_get_active_access_point()
      * nm_device_802_11_wireless_get_network_by_path ->
        nm_device_802_11_wireless_get_access_point_by_path
      * nm_device_802_11_wireless_get_networks ->
        nm_device_802_11_wireless_get_access_points

There was one API addition earlier today on the
org.freedesktop.NetworkManager D-Bus interface:

    <method name="GetActiveConnections">
      <!-- 'connections' is an array of structs
           consisting of the following elements:
               service name
               connection object path
               specific object
               array of (device object path)
      -->
      <arg name="connections" type="a(sooao)" direction="out"/>
    </method>

This allows the client to determine what specific connection is actually
active, or being activated, on which devices.  So, for example, if a
system settings connection was activated, the applet would be able to
figure out which exact one even though it was not the process that
provided that setting to NetworkManager.

Dan