On Tue, Jan 23, 2018 at 3:02 PM, Robert Tiemann <rtie(a)gmx.de> wrote:
On 01/21/2018 05:50 PM, Jose Blanquicet wrote:
>> My current client code constantly scans
>> for WLANs and reads out all data of all services on _any_ change
>> reported. Not very efficient, but it turned out to be the most
>> reliable way to keep up with changes.
> I would say that avoid doing that is exactly the reason why signals are used :)
I know, earlier versions of my client relied on signals, and I'd
prefer it this way.
It turned out, however, that some information were missing from the
signals. That is, I have often received a set of changes by signal,
but when reading out all services and checking for changes manually,
I've found more changes that were never reported by signal.
If you find something like this with latest version, try to get the
logs and a patter to reproduce the situation (If possible); then we
will try to fix it together :)