2013-12-16 13:16
82人阅读
评论(0)
收藏
举报
AndroidAnnotation
目录(?)[+]
Fork join
Since AndroidAnnotations 1.0
Fork / Join for the poor Android dev
Let's say you want to split a background operation into two separate operations that run concurrently, and then do something on the UI thread when both are done.假设你想将一个后台操作分成单独的两部分,并且需要同时运行,然后两部分都完成时在UI线程更新。
Here is a simple way to implement this, thanks to @Background
and @UiThread
.这里有一个简单的方法来实现,感谢 @Background
和@UiThread。
@EActivity public class MyActivity extends Activity { // Instances should only be accessed from the UI Thread to guarantee thread safetystatic class ResultHolder { ResultA resultA;ResultB resultB;} // Multiple clicks will start multiple distinguished computations@Click(R.id.myButton)void startForkableComputation() { ResultHolder resultHolder = new ResultHolder();computeResultA(resultHolder);computeResultB(resultHolder);}@Backgroundvoid computeResultA(ResultHolder resultHolder) { ResultA resultA = new ResultA();// Do some stuff with resultAjoinWork(resultHolder, resultA, null);}@Backgroundvoid computeResultB(ResultHolder resultHolder) { ResultB resultB = new ResultB();// Do some stuff with resultBjoinWork(resultHolder, null, resultB);}@UiThreadvoid joinWork(ResultHolder resultHolder, ResultA resultA, ResultB resultB) { if (resultA != null)resultHolder.resultA = resultA;if (resultB != null)resultHolder.resultB = resultB;if (resultHolder.resultA == null || resultHolder.resultB == null) { return;}// Show the results on the UI Thread}}
This works because we are joining the work in the Ui Thread, which is always the same thread. We also ensure that we always access ResultHolder
from the Ui Thread.合并工作总是在UI线程中进行,我们保证时刻访问 ResultHolder
。
Note by @pyricau: although I'm quite sure everything here is right and safe, I just received Java Concurrency in Practice from Amazon, so I'll read it with this fork / join use case in mind!Note by @pyricau:最然我很确信万事OK,但我刚刚收到来自Amazon的 Java Concurrency in Practice ,所以我会带着 fork / join 这个例子读这本书。