W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > April 2018

Re: [web-bluetooth] Handle notifications for characteristics missing a CCCD

From: Emill via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Apr 2018 22:50:45 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-381278753-1523659844-sysbot+gh@w3.org>
I wouldn't believe the mistake is that common. I mean for example all Android client tutorials online that deal with notifications show how to write the descriptor, so if people implement their peripheral wrong, they will notice that the descriptor is missing anyway if they connect to it from Android.

And peripherals set up using Android's GATT server api can easily be fixed by releasing app updates.

If this workaround is added, I suspect it rather can increase the amount of buggy devices, since they won't notice that they have done wrong. It even encourages this breaking of the rules since it would save one roundtrip since you don't need to write the descriptor then...

-- 
GitHub Notification of comment by Emill
Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/pull/391#issuecomment-381278753 using your GitHub account
Received on Friday, 13 April 2018 22:50:50 UTC

This archive was generated by hypermail 2.3.1 : Friday, 13 April 2018 22:50:51 UTC