You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Christopher Collins (JIRA)" <ji...@apache.org> on 2016/05/21 22:29:12 UTC
[jira] [Closed] (MYNEWT-295) BLE Host - Persist client
characteristic configuration for bonded peers
[ https://issues.apache.org/jira/browse/MYNEWT-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Collins closed MYNEWT-295.
--------------------------------------
Resolution: Fixed
> BLE Host - Persist client characteristic configuration for bonded peers
> -----------------------------------------------------------------------
>
> Key: MYNEWT-295
> URL: https://issues.apache.org/jira/browse/MYNEWT-295
> 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
(v6.3.4#6332)