On Monday 09 February 2015 18:11:43 Xu, Martin wrote: > So as to select the connectivity, at most situation, I think we should let > IoTivity as well as the platform to pick the proper connectivity technology > according to the performance and connectivity status of the platform. If > you have some specific example that application must select the > connectivity that will help a lot. ?
Actually, we can go a little further: if the device in question has multiple media available, which one(s) should the application pick? I would prefer an API that did the following: 1) make it easy to support ALL media and all networks in such media. That is, if the device has Ethernet, Bluetooth and WiFi, then it should be easy to tell IoTivity to simply listen in all media and broadcast services in all of them too. The user should not have to care which ones are available. Moreover, whenever possible, IoTivity should automatically add new networks as they become available and discard networks as they disappear. If necessary, it needs to notify the user of the fact that a network disappeared, so the user either drops any established state with peers in that network, or wait for it to come back. 2) make it possible to support a specific subset of media. Now, I don't know if we should provide a network enumeration API, so that the user can then pick. It seems far more likely to me that the using a subset of the media will happen only when the application knows exactly what devices it will run on and what will be available, do enumeration and monitoring seems unnecessary. How well does CA match those goals? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
