Hi Charitha,
I have already initiated a new thread[1] for this with bit different
architectural approach. So shall we discuss the design in there?
+1
Regards,
Inosh
On Thu, Mar 16, 2017 at 1:52 PM, Charitha Goonetilleke
wrote:
> Hi All,
>
> I have already initiated a new thread[1] for this wit
Hi All,
I have already initiated a new thread[1] for this with bit different
architectural approach. So shall we discuss the design in there?
[1] SDK approach for IoT Android Agent
On Thu, Mar 16, 2017 at 10:17 AM, Inosh Perera wrote:
> Hi Sumedha/Ruwan,
>
> Why this has to be special for Andr
Hi Sumedha/Ruwan,
Why this has to be special for Android?
I don't think we can write a SDK for iOS or windows since they are done by
the OS.
+1 for having generalisation for other device types such as raspberry pi
and arduino.
Plus, the more than calling the last segment, communication API, it sh
Yes, this should be a generic API. Plus, the more than calling the last
segment, communication API, it should be quoted configuration API, as
communication protocol, in reality is just a configuration given that said
configuration is supported.
Thanks and Regards,
Ruwan Yatawara
Associate Techni
Why this has to be special for Android? It's the generic API we provide
from IoT Server. And current API has part of this functionality. Isn't it?
On Thu, Mar 16, 2017 at 8:59 AM, Inosh Perera wrote:
> Hi All,
>
> Based on Charitha's suggestion to have an SDK for developers, I would
> suggest we
Hi All,
Based on Charitha's suggestion to have an SDK for developers, I would
suggest we have the following high level APIs made available for developers
as an Android SDK. This will contain functionalities of the existing
Android agent and it can be utilized to build agent's faster for different
