Re: [Architecture] [IoT] Load Distribution for Device + Server Communication.

Hi, IMO we can send a timeout with the operation which, once the operation/ notification is received by the device, it waits for the given timeout and respond back to the server to perform the operation. All operations are sent to devices at ones and the timeout should be different to each

Re: [Architecture] [IoT] Load Distribution for Device + Server Communication.

Hi All, I think it is better to have a solution which could be implemented in server side to distribute operations among devices. Because as we know device agents in IoTS devices are different to each other. In according to our architecture, we are letting anyone to write their own device types

Re: [Architecture] IdentityStore APIs in C5

On Mon, Feb 27, 2017 at 6:52 PM, Omindu Rathnaweera wrote: > We already have a JIRA[1] and a redmine for this. > > One requirement I came across was to identify when we are adding a > duplicate user. ATM we don't have a method to identify without checking > 'isUserExist'. It's

[Architecture] [IoT] Load Distribution for Device + Server Communication.

Hi all, We have encountered an issue with balancing load distribution of device + server communication. Device and server communication happens through following ways. 1. Polling - Device keeps polling the server 2. Push notification - Server sends a notification to device to come

Re: [Architecture] IdentityStore APIs in C5

We already have a JIRA[1] and a redmine for this. One requirement I came across was to identify when we are adding a duplicate user. ATM we don't have a method to identify without checking 'isUserExist'. It's better if we can at least introduce an error code for this. @Gayan might have come