- From: pzboyz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Nov 2015 15:13:49 +0000
- To: public-web-bluetooth-log@w3.org
Truly low power devices will be setting connection intervals of +100ms, and it is highly likely that only one GATT operation may be handled per connection interval, arguably the page author does not need to know the GATT operations have entered a queue, but it will need to know which ones have been executed. Imagine a case where the web page has written to a characteristic expecting the device behaviour to change, if that operation is 4th in the queue, the device may still send notification indicating it is still performing with the previous old behaviour, what is the web page to do given that it thinks the GATT operations have already been sent? -- GitHub Notification of comment by pzboyz Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/188#issuecomment-159935706 using your GitHub account
Received on Thursday, 26 November 2015 15:13:50 UTC