aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2010-01-04 14:33:44 (GMT)
committerJouni Malinen <j@w1.fi>2010-01-04 14:33:44 (GMT)
commit27f43d8de5161a77d14e39ccbd0ae5cc8cc0e582 (patch)
treef8c4244b3f5b04c1e7f21ae03fc23d30c0bc2472 /doc
parenta2753c285fc0efc5f65138d8f95de1e903b0fa31 (diff)
downloadhostap-27f43d8de5161a77d14e39ccbd0ae5cc8cc0e582.zip
hostap-27f43d8de5161a77d14e39ccbd0ae5cc8cc0e582.tar.gz
hostap-27f43d8de5161a77d14e39ccbd0ae5cc8cc0e582.tar.bz2
dbus: Replace StateChanged with PropertiesChanged signal
The actual supplicant state is exposed via a property on the interface object. So having a separate signal StateChanged for notifying about changes is a bad idea. The standard PropertiesChanged signal should be used for this. The advantage of StateChanged signal was that it includes the previous state, but not even NetworkManager is making use of this. And tracking the old state via the property and this signal is easily possible anyway.
Diffstat (limited to 'doc')
-rw-r--r--doc/dbus.doxygen14
1 files changed, 1 insertions, 13 deletions
diff --git a/doc/dbus.doxygen b/doc/dbus.doxygen
index 9deb28d..9b7dff2 100644
--- a/doc/dbus.doxygen
+++ b/doc/dbus.doxygen
@@ -406,18 +406,6 @@ fi.w1.wpa_supplicant1.CreateInterface.
</li>
<li>
- <h3>StateChanged ( s : newState, s : oldState )</h3>
- <p>Interface state has changed.</p>
- <h4>Arguments</h4>
- <dl>
- <dt>s : newState</dt>
- <dd>A state which the interface goes to</dd>
- <dt>s : oldState</dt>
- <dd>A state which the interface goes from</dd>
- </dl>
- </li>
-
- <li>
<h3>BSSAdded ( o : BSS, a{sv} : properties )</h3>
<p>Interface became aware of a new BSS.</p>
<h4>Arguments</h4>
@@ -501,7 +489,7 @@ fi.w1.wpa_supplicant1.CreateInterface.
<h4>Arguments</h4>
<dl>
<dt>a{sv} : properties</dt>
- <dd>A dictionary with pairs of properties names which have changed and theirs new values. Possible dictionary keys are: "ApScan", "Scanning", "CurrentBSS", "CurrentNetwork"</dd>
+ <dd>A dictionary with pairs of properties names which have changed and theirs new values. Possible dictionary keys are: "ApScan", "Scanning", "State", "CurrentBSS", "CurrentNetwork"</dd>
</dl>
</li>
</ul>