Windows also has address-to-string conversion routines when using Bluetooth sockets.
That said, BLE is not an "OCF" supported transport, and personally I see no need for it to be, given there's two other alternatives that already exist today: a) run OCF protocols over IP over BLE b) use a bridge to map to existing Bluetooth profiles > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Wednesday, August 3, 2016 11:36 PM > To: iotivity-dev at lists.iotivity.org; jihwan.seo at samsung.com; JinHyeock > Choi > <jinchoe at gmail.com> > Subject: Re: [dev] OCF Endpoint Implement on iotivity > > On quinta-feira, 4 de agosto de 2016 04:04:59 PDT ??? wrote: > > I understand that reason. > > but when BLE is defined in the near future. > > some problem will be caused because there is no public API like > > getAddress() in any Bluetooth Platform. > > On Linux, the hciconfig can display the address. That implies that it can be > obtained from the kernel. strace identifies these operations: > > socket(AF_BLUETOOTH, SOCK_RAW, 1) = 3 > ioctl(3, HCIGETDEVLIST, 0x55e18eaca010) = 0 ioctl(3, HCIGETDEVINFO, > 0x55e18cc3bac0) = 0 > > Can't you use that to get the device's own address? > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
