W3C home > Mailing lists > Public > public-web-bluetooth@w3.org > August 2014

Re: Notes from meeting between Chrome and Mozilla folks

From: Vincent Scheib <scheib@google.com>
Date: Fri, 8 Aug 2014 14:51:58 -0700
Message-ID: <CAK-EfXkZaEhVfRF-gvuizbAj0BnR4oinYY9i2rGRBrdSyDeb4g@mail.gmail.com>
To: Shawn Huang <shuang@mozilla.com>
Cc: public-web-bluetooth <public-web-bluetooth@w3.org>, Jeffrey Yasskin <jyasskin@google.com>, Marcos Caceres <marcos@marcosc.com>
I agree on the 2 points:
- Need a way to accept UUID per Bluetooth spec for non standard services
- Identifying standard services via their name vs full or short UUID makes
sense. Let's do functionName("standard_gatt_service_name")

On Fri, Aug 8, 2014 at 12:49 PM, Shawn Huang <shuang@mozilla.com> wrote:

> >> 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 Friday, 8 August 2014 21:52:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:52 UTC