On Sat, Jul 16, 2011 at 9:35 AM, DCA wrote:
> Am I right in assuming that there is no way to forceably stop a
> misbehaving thread within an Android application short of killing the
> process that owns the thread? My problem is that I'm loading java-
> based plug-ins (not ARM binaries) into my fra
Thanks for the insights, Mark.
Am I right in assuming that there is no way to forceably stop a
misbehaving thread within an Android application short of killing the
process that owns the thread? My problem is that I'm loading java-
based plug-ins (not ARM binaries) into my framework dynamically (u
On Wednesday, July 13, 2011 9:16:56 AM UTC-4, DCA wrote:
I've developed a framework that loads potentially untrusted plug-in
> code from a remote repository into my framework's process at runtime
> (using OSGi). Each plug-in is started on a thread that my framework
> holds a reference to. Probl
On Sat, Jul 16, 2011 at 7:15 AM, DCA wrote:
> however, do applications with multiple processes share the same memory
> space, or is AIDL required to communicate between components running
> in a separate process, even though they are both part of the same
> application?
They do not share the same
On the dev page describing Processes and threads (link below), it
states that "By default, all components of the same application run in
the same process and most applications should not change this.
However, if you find that you need to control which process a certain
component belongs to, you can
Hi,
Can you framework load these untrusted Threads into a separate
process ? If yes just kill that process.
Regards
On Jul 13, 11:16 pm, DCA wrote:
> I've developed a framework that loads potentially untrusted plug-in
> code from a remote repository into my framework's process at runtime
> (usi
6 matches
Mail list logo
