All,
We've been working on this architecture for a long time now. Lets have a
comprehensive review on Friday. I've already sent out the invite.
On Mon, Nov 24, 2014 at 7:00 AM, Shan s...@wso2.com wrote:
Hi all,
Just to add some points .
That depends on whether an agent is involved or not
3
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
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 dil...@wso2.com wrote:
Hi All,
Why do we need to construct a
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.
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
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
Hi Harshan,
This is with reference to the two merging options that you have mentioned
in your previous reply to the thread.
As I understood, with the 1st Option:
You suggest to
[1] convert platform-independent-payload to platform-specific-payload, save
it and when another request comes in,
[2]
Hi Dilan,
Yes. you are correct.
Thanks,
Lakshitha Harshan
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com http://wso2.com/*
lean.enterprise.middleware.
On Tue, Nov 18, 2014 at 7:20 AM, Dilan Udara Ariyaratne
Hi,
*Platform-specific payload *is the actual payload which will be delivered
to the device when the device contacts the server for
pending-operations. *Platform-independent
*form is used to construct the *Platform-specific payload * communicate
device operations internally within CDM. For
Hi,
Please find the attached proposed device operations flow of CDM. Your
suggestions feedback is highly appreciated.
Thanks,
Best Regards,
Lakshitha Harshan
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com
Hi Harshan,
If for example, a message to a device is already in the queue and when
monitoring happen, a similar payload is generated. How is it handled when
it comes to communication between out queue and device platform bundle?
Regards,
Inosh
On Mon, Nov 3, 2014 at 3:20 PM, Harshan Liyanage
Hi InoshP,
Before explaining the above scenario I'll explain the process of payload
generation when a request for new operation comes to the CDM core.
1. CDM Core bundle will detect its device platform using the operation code
2. Validate the operation against the supported device operations
3.
Hi Harshan
1. Device platform bundle will take the platform-specific payload in the
queue merge it with the new operation
In this case, the overhead of the device platform bundle will be much
higher because it must know how to convert back the *platform-specific
payload* to the
Hi Niranjan,
Please find my comments in line.
IMO this would be the a better option since the overhead is removed when
the device tries to communicate with the server to get the payload. AFAIU
even in the option 2 and 3, the device platform bundle should be able to
convert the
14 matches
Mail list logo
