[
https://issues.apache.org/jira/browse/MYNEWT-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William San Filippo resolved MYNEWT-385.
----------------------------------------
Resolution: Fixed
Fix has been committed and tested. NOTE: the controller does not autonomously
issue a connection parameter request control procedure currently. If we add
code to the controller to do such, the current fix would end up sending the
host of the slave a connection update complete event even though the host did
not request one. The spec says that the controller should not do this. This is
a moot point now but if this feature gets added to the controller this code
would have to change.
> Controller does not send connection update to host if connection is a slave
> and only an anchor point change was requested
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: MYNEWT-385
> URL: https://issues.apache.org/jira/browse/MYNEWT-385
> Project: Mynewt
> Issue Type: Bug
> Components: Nimble
> Affects Versions: v0_9_0
> Reporter: William San Filippo
> Assignee: William San Filippo
> Fix For: v1_0_0_beta1
>
>
> The nimble controller was not sending a connection update complete event in
> the following circumstances:
> 1) The connection role is slave.
> 2) The host initiates the connection parameter request.
> 3) Only an anchor point move occurs.
> The specification could be worded in a more unambiguous way, but it does seem
> that the host should be notified every time it initiates a connection
> parameter request or update.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
