[
https://issues.apache.org/jira/browse/MYNEWT-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468593#comment-15468593
]
ASF subversion and git services commented on MYNEWT-385:
--------------------------------------------------------
Commit 97189e716b11ab59599a7693e838f9ccf51c071f in incubator-mynewt-core's
branch refs/heads/master from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=97189e7
]
MYNEWT-385: Controller not sending connection update complete event
The nimble controller was not sending the connection update
complete event if the connection was a slave, the host initiated
the connection parameter request and only an anchor point move was
requested. The spec is not perfectly clear but it seems this was a
bug and that the host should always be notified if it initiates
the connection update or connection parameter request.
> 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)
