Re: [Architecture] [AppManager] Sorting Applications in the store by accessed fequency

Hi, In addition to my previous mail, instead of directly writing to a DB, periodically we are publishing the events to BAM for analysing and processing so it will run in a different thread. On Fri, Nov 21, 2014 at 11:00 PM, Pulasthi Supun wrote: > Hi All, > > The method that Udara mentioned

Re: [Architecture] Proposed Device Operations Flow of CDM

Hi All, Why do we need to construct a "Platform-specific-payload" at the server level? Cannot we just send the "Platform-independent-payload" to the device agent and invoke the corresponding feature operation at the client side? I might not be right because I am not exactly aware of all the use-

Re: [Architecture] Proposed Device Operations Flow of CDM

Hi Dilan On Windows and iOS we need to use the specific protocols and rely on the OS to execute the command. This is why we have to use this approach. (Sent from a mobile device) On 22 Nov 2014 19:29, "Dilan Udara Ariyaratne" wrote: > Hi All, > > Why do we need to construct a "Platform-specific-

Re: [Architecture] RFC: Extending Siddhi Language to Handle Batch Processing

Hi all, +1 for the idea. IMO using the *from* clause on event tables to do batch processing makes sense and fits the current Siddhi model nicely. For supporting the *from* clause when the timestamp is not given, can we add a timestamp internally to the table if the event table definition does not

Re: [Architecture] Proposed Device Operations Flow of CDM

Hi Sameera, I am not exactly getting the point. It should be because I am not exactly aware of the actual use case of Windows and iOS. Do you mean that they are using different transport (or connectivity) protocols? Regards. *Dilan U. Ariyaratne* Software Engineer WSO2 Inc.

Re: [Architecture] Proposed Device Operations Flow of CDM

Hi Dilan, In the case of iOS, it has the MDM in its OS and they have defined the payload structure for each operation. Whereas in the case of Android, we have an agent in the client side to perform the MDM operation. I believe (please correct me if am wrong) that for windows also it is the same ca

Re: [Architecture] Proposed Architecture of CDM

Hi All, I am having this little doubt about the use and the purpose of having a device-specific OSGI Bundle at the server side. By doing that, aren't we taking up the burden of handling all the complexities/incompatibilities of the device side to the server side. Isn't that possible to move this

Re: [Architecture] Proposed Device Operations Flow of CDM

Hi Dilan, The main reason why we send a platform specific payload to the device is because the Device might not be capable of performing intelligent filtering as required. In the case of Android - we can do it because of our agent. But for iOS/Windows this is not possible cause the MDM operations a

Re: [Architecture] Proposed Architecture of CDM

Hi Dilan, The main use case for the CDM is to manage any device. To do this - we have to perform intelligent management at the server side rather than giving that to the client. This is due to below reasons :- - The client might not be written by us - Support DM protocols (OMA DM/ LW M2M)