+1 for the 3 options Shan mentioned. This will depend on the requirement. Cheers~
On Thu, Apr 10, 2014 at 12:07 PM, Kasun Dananjaya Delgolla <[email protected]>wrote: > Hi Shan, > > Yes it is possible. I will start working on this when I'm done with OAuth > implementation. > > Thanks > > > On Thu, Apr 10, 2014 at 11:51 AM, Shanmugarajah Sinnathamby <[email protected] > > wrote: > >> There are cases where we have to go with the specific approaches like >> local push notification only, GCM only or both . >> So if we can configure the system in a way where 3 scenarios are possible >> . >> 1. Local Notification Only (Currently this is one of the customer >> requirement) >> 2. GCM only >> 3. Hybrid (Local + GCM) Option to select Local Notification for >> Compliance monitoring and manual push to use GCM. >> >> >> On Thu, Apr 10, 2014 at 10:56 AM, Dilshan Edirisuriya >> <[email protected]>wrote: >> >>> I believe its better to use them both since in some scenarios if we have >>> dynamic policies (time based etc. ) which is created from EMM this will be >>> needed. Hence we need to think about a way to have them work when >>> necessary. >>> >>> >>> On Thu, Apr 10, 2014 at 10:45 AM, Kasun Dananjaya Delgolla < >>> [email protected]> wrote: >>> >>>> @Dilshan - We can actually allow switching. But there might be a >>>> scenario where we might need both. That's totally depends on the scenario >>>> where it will be used. >>>> >>>> >>>> On Thu, Apr 10, 2014 at 10:41 AM, Chathura Dilan <[email protected]>wrote: >>>> >>>>> +1 for local notifications. There are some tasks which need to happen >>>>> real time and some tasks which does need to happen on time. If we can >>>>> distinguish them properly we can save large amount of battery power. >>>>> >>>>> >>>>> On Thu, Apr 10, 2014 at 10:34 AM, Harshan Liyanage >>>>> <[email protected]>wrote: >>>>> >>>>>> Hi Kasun, >>>>>> >>>>>> I think we must implement the method you are proposing. Since this >>>>>> AlarmManager system service will wakeup our EMM agent in every 10 mins >>>>>> (or >>>>>> in configured intervals) it will make sure that our EMM agent is running >>>>>> in >>>>>> the device. Otherwise there would be no way that we could guarantee that >>>>>> EMM-agent process is running in the device. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> Lakshitha Harshan >>>>>> Software Engineer >>>>>> Mobile: *+94724423048* >>>>>> Email: [email protected] >>>>>> Blog : http://harshanliyanage.blogspot.com/ >>>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>>>>> lean.enterprise.middleware. >>>>>> >>>>>> >>>>>> On Wed, Apr 9, 2014 at 9:33 PM, Kasun Dananjaya Delgolla < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> This is to brief and discuss about the architecture of the $subject. >>>>>>> So here's how it works. >>>>>>> >>>>>>> We gonna enable both GCM and Local push as switchable options so >>>>>>> that depending on the requirement, we can choose which method to go >>>>>>> with. >>>>>>> >>>>>>> Android's native service such as AlarmManager will be used to >>>>>>> trigger local notifications so that it will be very effective with >>>>>>> Battery >>>>>>> consumption. >>>>>>> >>>>>>> On Agent launch, if the selected method is local push, Agent will >>>>>>> initiate a repeating event using AlarmManager. (Ex: Repeat every >>>>>>> 10mins). >>>>>>> When the AlarmManager triggers the event, it simply get captured by the >>>>>>> Local Notification Receiver resides in our EMM Agent. And then it will >>>>>>> perform the necessary action (Operation/Contacting the server). >>>>>>> >>>>>>> I have already done a thorough testing on battery consumption using >>>>>>> this method which is less than 0.5% when this service is running every 5 >>>>>>> minutes with a web service call. >>>>>>> >>>>>>> Therefore this can actually be used as an alternative to GCM. And it >>>>>>> can also be used to capture violations (If the device is stolen and the >>>>>>> network is switch off etc) and implement a self initiation protocol in >>>>>>> such >>>>>>> cases. But IMO we should keep both the options because those 2 can come >>>>>>> handy in different situations. >>>>>>> >>>>>>> So WDYT? >>>>>>> >>>>>>> Given below is how Android EMM Agent will look like, >>>>>>> >>>>>>> [image: Inline image 1] >>>>>>> >>>>>>> If you want an in-depth diagram on the current EMM Agent >>>>>>> Architecture [1]. >>>>>>> >>>>>>> >>>>>>> [1] - >>>>>>> https://docs.google.com/a/wso2.com/drawings/d/12LOSMJxPtcI_XXjkD5RnPp-uaJGTFtCC-MXkmPLT4LY/edit?usp=sharing >>>>>>> >>>>>>> Thanks >>>>>>> -- >>>>>>> Kasun Dananjaya Delgolla >>>>>>> >>>>>>> Software Engineer >>>>>>> WSO2 Inc.; http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> Tel: +94 11 214 5345 >>>>>>> Fax: +94 11 2145300 >>>>>>> Mob: + 94 777 997 850 >>>>>>> Blog: http://kddcodingparadise.blogspot.com >>>>>>> Linkedin: *http://lk.linkedin.com/in/kasundananjaya >>>>>>> <http://lk.linkedin.com/in/kasundananjaya>* >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> >>>>> Chatura Dilan Perera >>>>> *(Senior Software Engineer - WSO2 Mobile)* >>>>> www.dilan.me >>>>> >>>> >>>> >>>> >>>> -- >>>> Kasun Dananjaya Delgolla >>>> >>>> Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> Tel: +94 11 214 5345 >>>> Fax: +94 11 2145300 >>>> Mob: + 94 777 997 850 >>>> Blog: http://kddcodingparadise.blogspot.com >>>> Linkedin: *http://lk.linkedin.com/in/kasundananjaya >>>> <http://lk.linkedin.com/in/kasundananjaya>* >>>> >>> >>> >>> >>> -- >>> Dilshan Edirisuriya >>> Senior Software Engineer - WSO2 >>> Mob: + 94 777878905 >>> http://wso2.com/ >>> >> >> >> >> -- >> *Shanmugarajah (Shan)* >> Director Architecture, Enterprise Mobility >> WSO2, Inc.; http://wso2.com >> Email: [email protected] >> Mobile : +94777748260 >> Blog: http://shanfour.blogspot.com >> > > > > -- > Kasun Dananjaya Delgolla > > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > Tel: +94 11 214 5345 > Fax: +94 11 2145300 > Mob: + 94 777 997 850 > Blog: http://kddcodingparadise.blogspot.com > Linkedin: *http://lk.linkedin.com/in/kasundananjaya > <http://lk.linkedin.com/in/kasundananjaya>* > -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email [email protected] <[email protected]>* * ~Mobile +94712112165* * ~Website dulitha.me <http://dulitha.me>* * ~Twitter @dulitharw <https://twitter.com/dulitharw>* *~Github @dulichan <https://github.com/dulichan>* *~SO @chan <http://stackoverflow.com/users/813471/chan>*
<<inline: Local notifications - Android.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
