All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH 7/7] doc: document access point scanning
Date: Wed, 23 Feb 2022 12:43:31 -0600	[thread overview]
Message-ID: <db615d8d-a416-e3d2-ec7f-80ffdc5d1ead@gmail.com> (raw)
In-Reply-To: 20220222225718.2485794-7-prestwoj@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

Hi James,

On 2/22/22 16:57, James Prestwood wrote:
> ---
>   doc/access-point-api.txt | 27 +++++++++++++++++++++++++++
>   1 file changed, 27 insertions(+)
> 

<snip>

> +		array(dict) GetOrderedNetworks()
> +
> +			Gets the list of networks found after scanning sorted
> +			based on signal strength. Each item in the array is a
> +			dictionary containing the network Name, SignalStrength,
> +			and Security.

Security -> Type to be consistent with KnownNetwork / Network interface naming 
of the properties.

> +
> +			This list will expire similarly to station, and since
> +			access points do not do periodic scans the list may
> +			become empty after some time and requires scanning
> +			again.

I'm not sure what this is about?  Scan results don't actually expire in Station 
in the sense that you can keep calling GetOrderedNetworks() forever and get the 
same results, as long as scanning hasn't been performed.  Essentially if 
Scanning hasn't changed, GetOrderedNetworks() results shouldn't change either.

I would expect the same behavior here?

Regards,
-Denis

             reply	other threads:[~2022-02-23 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 18:43 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-23 20:18 [PATCH 7/7] doc: document access point scanning James Prestwood
2022-02-22 22:57 James Prestwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db615d8d-a416-e3d2-ec7f-80ffdc5d1ead@gmail.com \
    --to=unknown@example.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.