Thanks for the feedback. > but what happens when you hit a > deadzone or you have a weak 3g signal? Depends on the implementation, but there could be two scenarios: a) If the application is starting a new thread while in a low reception area, then the task would automatically execute locally on the device instead. This would obviously make it a lot slower, but at least the computation would still happen. From the developers perspective, this would happen transparently. b) If the thread was started while the device was well connected and the device then subsequently moves into a low reception area, then the device gets the results from the computation when it gets connected again, or alternatively falls back to performing the calculations locally if it doesn't reenter a region with better reception within some fixed amount of time.
> How about any security issues? I can immediately think of two concerns: * 3rd parties tapping into the traffic between the device and the cloud service: solved by using TLS. * processes interaction and interference on the cloud servers: solved through sandboxing. Additionally there could be some privacy concerns if sensitive data is moved back and forth between the device and the cloud service. For how long can it be retained on the cloud servers (caching etc). Policies would have to be in place to safeguard this. Do you have any additional concerns? Thanks for taking the time to reply! All the best, Sebastian -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
