> Assuming you mean Java Threads, I guess you are talking about being > able to execute arbitrary (classes that implement) Runnable in a JVM > in the cloud ? Correct. Only that you would replace Runnable with some other sub- interface with some additional methods.
> A Thread & Runnable has no inherent comms for returning the results of > the execution from the cloud back to the device, your framework would > need to provide this - there is a multitude of options. Yes, that is correct. It would be a thread/actor hybrid with means of sending messages back and forth between the device and the server. > - I think you must still handle the 'turing halting problem' issue > where some code might have gone into an infinite loop and must be > stopped eventually There are cases where you would want a thread to be able to run indefinitely. It could do some period task. Check some resources at given intervals and report back to the device whenever the application is running. When that is not the desired property of the threads, one could also enforce the rule that the remote threads are killed when the application terminates. > so you would still need hard limits to interrupt this sort of code, I think hard limits can be avoided. Of course you might want them in certain circumstances, but not always. > > I would also be interested in what java api's would be available to > the thread when it is running in the cloud - all of the Android sdk or > j2se or j2ee, or some whitelist as per App Engine ??? I think there is > some issues that would make it difficult for you to provide the full > android sdk in the cloud, eg ndk integration and performance in > general - if you were for example, running instances of the Android > emulator in the cloud and using these as your vm / jvm 'cloud based > thread engine'. Some research has been done where the code executed remotely ran in an android vm. I am not at liberty of discussing this research freely as it isn't mine, but initial tests showed great performance increases over executing the code locally. > Perhaps you can create a demo app and publish the code and performance > details. In due time a prototype and demo will be published. For now I just wanted to get some general feedback from android developers to see if there was any interest for a system like this at all in the developer community. Thanks for following up! 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.
