On Fri, Mar 25, 2016 at 10:10:47AM -0700, aditi hilbert wrote: > Can the specific HCI package be part of the target definition instead > of the app? That way apps could remain HCI-transport agnostic. > Just a thought.
I do think that would be ideal. The only issue is that some code has to initialize the specific HCI transport package being used. The target does not contain any code, so this would need to be done by some other package (e.g., the app). I was thinking about some sort of "generic HCI facade" package (or something) which initializes the correct HCI transport. That would allow the app to be agnostic with regards to the HCI transport being used. However, this started to feel way too complicated to justify implementing it, so that's when I stopped thinking about it :). There is probably a simpler solution that I haven't considered, so if anyone has any ideas, please share them. I think the example BLE apps (bletiny and bleprph) are exceptional in that they are not developed for any specific platform. My thinking is that most developers will know exactly which HCI transport they will be using from the start, so this whole concern of mine may end up being a nonissue. Chris
