- From: Shawn Huang <shuang@mozilla.com>
- Date: Fri, 8 Aug 2014 12:49:58 -0700 (PDT)
- To: public-web-bluetooth <public-web-bluetooth@w3.org>
- Cc: Vincent Scheib <scheib@google.com>, Jeffrey Yasskin <jyasskin@google.com>, Marcos Caceres <marcos@marcosc.com>
>> But >> service UUIDs are designed to efficiently solve that. > If the strings are unique, as it the case with the enum, I don't see how using a UUID is more efficient? The are both unique strings. It makes sense to let browser automatically map human readable string to UUID internally for Bluetooth SIG assigned number(ex: Service/Characteristics), this will make JS easier to write/read if developers want to implement standard GATT profiles. But we still need API to accept UUID as the parameter for those vendor specific defined GATT Profiles (it contains their own Service/Characteristic UUID).
Received on Monday, 11 August 2014 13:44:02 UTC