You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2019/06/25 17:26:34 UTC

[GitHub] [mynewt-nimble] ccollins476ad commented on issue #500: nimble/gatt: Add the following sanity checks for Notify/Indicate

ccollins476ad commented on issue #500: nimble/gatt: Add the following sanity checks for Notify/Indicate
URL: https://github.com/apache/mynewt-nimble/pull/500#issuecomment-505542584
 
 
   I'll let others weigh in, but I don't think the host should check for the presence of a CCCD before sending notifications / indications.
   
   In my mind, there is a distinction between subscribing to notifications vs. sending them. A CCCD is required for subscribing, not for sending.  I don't think the spec prohibits sending notifications for a characteristic without a CCCD.
   
   Also, I didn't totally understand what `now` means in the new function names.  To me, "now" means immediately, but the `now` parameter doesn't affect when the notification gets sent.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services