Saturday, July 6, 2013

[android-developers] Re: Fork/Join and JSR166 on Android

Ratamovic:

Why on earth would you want to use a dynamic decomposing framework in Android? These things only work well when there are many, many processors to handle the splits. Such a framework would kill a phone/tablet; you would process one task at the expense of everything else.

If you're looking to split work into multiple threads,  then there are products to do just that. I wrote this article and the software it expounds: Managing Threads in Android

Ed

On Tuesday, July 2, 2013 6:00:35 PM UTC-4, Ratamovic wrote:
Hi all,

I am trying to find some information about the support of the new Fork/Join framework introduced in Java7 (JSR166).
Of course Android doesn't support Java 1.7 (yet at least) but a Java6 (limited) backport of Fork/Join exists (see jsr166 http://gee.cs.oswego.edu/dl/concurrency-interest/). I am curious to know if anybody had experience with using it on Android.

The subsidiary question would be about the use of any other concurrent framework on Android (like Akka, etc.). Any feedback?

Thanks in advance!

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate