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 <[email protected]> wrote: > 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 > types of Android devices such as TVs or wearables. > > Enrollment API > This will provide Oauth based and mutual SSL based authentication flows > OOB including UIs where the developer simply need to call the needed flow > and and can get a device enrolled. This flow should also facilitate > plugging in any new authentication flows, so that if the developer need a > different authentication mechanism, it can be facilitated. > > Device API > This will simply provide access to different SDKs methods in Android so > that the developer doesn't need to deal with for example location services > to get the current location. This may also include sensor data querying. > > Application API > This API provides capabilities to handle application management related > tasks such as app installs, uninstall, updates and get application related > information on device. > > Policy API > This will provide policy enforcement and policy monitoring related APIs. > When a policy enforcement request comes from the server, relevant policy > API must be called to enforce it and the monitoring API provides ability to > check if the enforced policy is adhered by the device. > > Operation API > This will have APIs necessery to schedule polling the server to get > operations to be executed and and a default implementation of an operation > manager which talks to different APIs such as device API, Application API > or policy API based on the operations received from the server. > > Communication API > This will provide different communication methods such as Http, mqtt or > listeners for FCM. API should provide mechanism to plugin any user needed > protocols to communicate with the IoT server. This API will also provide > means to talk to other applications such as system application or App > catalog application which are already available. > > This is a basic high level API view. Please provide your suggestions. > > Regards, > Inosh > > > -- > Inosh Perera > Senior Software Engineer, WSO2 Inc. > Tel: 077813 7285, 0785293686 <078%20529%203686> > -- /sumedha m: +94 773017743 b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
