This separates the BSSID informational requests from the main path so that can
be done asynchronous and interleaved with more important requests. This way, if
there is a massive flurry of BSSID notifications, processing those notifications
(even though it's usually quick) will not delay handing of notifications.
This refactoring was originally done since it was hypothesized that
notifications would queue up and eventually get dropped at the Unix domain
socket level. This wasn't happening. However, since BSSID info requests have
been dropped by the wpa_supplicant, this separation feels "good" since it
opens up oportunities to reduce redundant requests and possibly to batch updates
together to minimize the overhead of dealing with tons of incremental AP
notifications.
Move BSSID requests to a separate process
This separates the BSSID informational requests from the main path so that can be done asynchronous and interleaved with more important requests. This way, if there is a massive flurry of BSSID notifications, processing those notifications (even though it's usually quick) will not delay handing of notifications.
This refactoring was originally done since it was hypothesized that notifications would queue up and eventually get dropped at the Unix domain socket level. This wasn't happening. However, since BSSID info requests have been dropped by the
wpa_supplicant, this separation feels "good" since it opens up oportunities to reduce redundant requests and possibly to batch updates together to minimize the overhead of dealing with tons of incremental AP notifications.