mynewt-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Collins (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MYNEWT-842) BLE Host - Handle failure to add entry to resolving list
Date Tue, 17 Oct 2017 23:10:00 GMT

     [ https://issues.apache.org/jira/browse/MYNEWT-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher Collins resolved MYNEWT-842.
----------------------------------------
    Resolution: Fixed

> BLE Host - Handle failure to add entry to resolving list
> --------------------------------------------------------
>
>                 Key: MYNEWT-842
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-842
>             Project: Mynewt
>          Issue Type: Bug
>      Security Level: Public(Viewable by anyone) 
>          Components: Nimble
>            Reporter: Christopher Collins
>            Assignee: Christopher Collins
>             Fix For: v1_3_0_rel
>
>
> (Pull request: https://github.com/apache/mynewt-core/pull/596)
> If an attempt to add a peer's IRK to the resolving list fails, the failure is not reported,
and the operation is not reattempted.  Adding to the resolving list fails if the host is scanning
or advertising at the time, so this is a common occurrence.
> I am not sure what the best solution is to this problem.  I have a few ideas (order of
increasing complexity):
> 1. The host stops all active GAP procedures before trying to add the entry to the resolving
list.  The application must restart interrupted procedures as needed.
> 2. The host passes the necessary information up to the application.  It is then up to
the application to populate the resolving list when possible (or not).
> 3. The host remembers the failed attempt and retries when in a suitable state (i.e.,
when advertising, scanning, and connecting has stopped).
> 4. The host temporarily suspends all GAP activity, adds the entry to the resolving list,
and resumes GAP activity.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message