mynewt-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Collins (JIRA)" <>
Subject [jira] [Closed] (MYNEWT-295) BLE Host - Persist client characteristic configuration for bonded peers
Date Sat, 21 May 2016 22:29:12 GMT


Christopher Collins closed MYNEWT-295.
    Resolution: Fixed

> BLE Host - Persist client characteristic configuration for bonded peers
> -----------------------------------------------------------------------
>                 Key: MYNEWT-295
>                 URL:
>             Project: Mynewt
>          Issue Type: New Feature
>          Components: Nimble
>            Reporter: Christopher Collins
>            Assignee: Christopher Collins
> h2. Current Behavior
> When a peer enables notifications or indications via a write to a client characteristic
configuration descriptor, the change only lasts for the lifetime of the connection.
> h2. Proposed Change
> The current behavior is correct for non-bonded connections.  However, for bonded peers,
the values of the client characteristic configuration descriptors should persist across connections.
 Here are a few notes about the desired behavior:
> * The persisted configuration is restored when a bonded connection is restored.
> * The peripheral should remember whether a characteristic changed, even if particular
peer is not connected.  When the peer connects and the client characteristic configuration
is restored, a notification or indication should be sent immediately if appropriate.

This message was sent by Atlassian JIRA

View raw message