Thanks for taking the time to comment. It definitely is an additional layer of complexity, but the idea would be to minimize that complexity from the developers point of view by letting these special threads be used in places of regular threads where threads would be used anyway. The threads would only move the computation to the cloud if there is sufficient bandwidth available. Networks are inherently flaky and unreliable, so one would have to plan for failed and changing connections, but this would be abstracted away.
There is also the class of applications that rely on being connected to the internet to work. Often backed up by some kind of web service. Development of such applications would become significantly easier as all the code would live directly in the same codebase. Additionally capacity planning for such services becomes easier as you would only be charged for the actual computations being executed rather than having idle cloud capacity you need to maintain and pay for yourself. All the best, Sebastian On Dec 26, 2:09 am, "Maps.Huge.Info (Maps API Guru)" <[email protected]> wrote: > To me, it sounds like an unnecessary layer of complexity that would > lead to locked up phones, failed apps and general unpleasantness for > the user. Keep it simple is the best possible plan. Then again, what > do I know? > > -John Coryat -- 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.
