[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 166050] Merge KWifimanager with KNetworkmanager and make a
From:       Stefan Winter <swinter () kde ! org>
Date:       2008-07-15 18:05:57
Message-ID: 20080715180557.27517.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=166050         
swinter kde org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Product|kwifimanager                |knetworkmanager



------- Additional Comments From swinter kde org  2008-07-15 20:05 -------
Hi,

thanks for the report. The thing is: KWiFiManager is pretty much dead. I discontinued \
it for KDE4, the idea being that KNetworkManager fills the gap.

I do acknowledge however that the scan interval in KNetworkManager is rather slow, \
and that entries in the table age out very slowly. This makes it difficult to get a \
comprehensive and current view over the available networks.

So, I support your wish, but I'll have to toss the report over to KNetworkManager. 

For the KNetworkManager people: back then, I used a scan interval of 250 ms. I'd \
suggest aging out the information after say 15 seconds after a given SSID was last \
seen.

Another popular feature in KWiFiManager that got lost in translation is the "acoustic \
scanning". Some people like to use this feature for finding networks in their \
vicinity without looking at their box. KNetworkManager could do this by \
(configurably) emitting its "ping" if wireless interfaces have >0 SSIDs.

Cheers,

Stefan Winter


[prev in list] [next in list] [prev in thread] [next in thread]