Hi Brian, Thanks for clarifying. On Mon, Dec 17, 2018 at 09:48:34PM +0000, Gix, Brian wrote: > I consider this to be a practical approach, because the overhead > consumed by ACL connections negatively affects Advertising based > communications, and linux in particular handles a practically > unlimited number of controllers. Support for devices with controllers > that have active ACL connections requires other mesh devices to send > more redundant packets to ensure delivery. Ok, fair enough. We are well aware of performance considerations. What I'm thinking about is having both modes of communication available, even if the embedded device has just one Controller, as is the case with the majority of off-the-shelf platforms. The reason we want/need both BLE/GATT and Mesh on the same node has a lot to do with provisioning - at the moment we configure our networks using a mobile app, meaning we need devices to support PB-GATT. This is because Controllers present in mobile devices do not support Mesh natively, and we can't assume there is a GATT Proxy nearby, especially when configuring a new network. > And I am not opposed to someone starting a project that will allow the > bluetoothd and meshd share a single controller and taking > responsibility the reduced performance of each, but that is not work > we have planned. Ack. FYI, it seems we might be interested in making that happen. regards -- Michał Lowas-Rzechonek <michal.lowas-rzechonek@xxxxxxxxxxx> Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND
