Asynctask from non ui thread

Question

Is it a must that we have to initiate and execute asyctask from UI thread.Is it correct if i use asynctask for a webservice access(long running) from a non ui thread. sorry if my query is wrong.

In my app i have to run around 10 webservices and have to show the result on ui .i am confused which approach will be good asynctask,intentservice or creating thread for each webservice call and making it to run parallel.

what about my answer try that......u can reuse the same code to call different type web services without blocking UI thread — Pragnani, Jan 23 '13 at 19:39

Rahul Verma · Answer 1 · 2013-01-23T20:13:17.383

2

There are a few threading rules that must be followed for AsyncTask to work properly:

The AsyncTask class must be loaded on the UI thread. This is done automatically as of JELLY_BEAN.
The task instance must be created on the UI thread.
execute(Params...) must be invoked on the UI thread.
Do not call onPreExecute(), onPostExecute(Result), doInBackground(Params...), onProgressUpdate(Progress...) manually.
The task can be executed only once (an exception will be thrown if a second execution is attempted.)

Further Details

In my personal opinion, I would suggest using AsyncTask as it is highly optimized for running background tasks and exploit benefits like multicore processor.

edited Jan 23 '13 at 20:13

answered Jan 23 '13 at 19:00

Rahul Verma

2,140
3
21
31

1

this is false, an `IntentService` does not need an AsyncTask, it already runs in the background `IntentService is a base class for Services that handle ASYNCHRONUS requests (expressed as Intents) on demand.` http://developer.android.com/reference/android/app/IntentService.html – tyczj Jan 23 '13 at 19:13
@tyczj What you've said is true, but so is Rahul's answer, although it *might* not answer the OP. He didn't say anything about IntentService using an AsyncTask. I suspect that the OP needs IntentService though. – Simon Jan 23 '13 at 20:50
@Simon Yes I was only talking about the intentservice part being wrong – tyczj Jan 23 '13 at 21:09

score 0 · Answer 2 · answered Jan 23 '13 at 18:58

0

Yes, asynctask needs to be run from the UI thread.

I'd suggest to use multiple threads/runnables. You'll also need to implement a handler in your main activity class to listen to the responses from the threads.

answered Jan 23 '13 at 18:58

paulczak

96
6

score 0 · Answer 3 · answered Jan 23 '13 at 19:01

0

You can go with either thread or asynctask. AsyncTask provide you methods to manage Ui changes methods before starting background task and after finishing backgroung task or getting its progress.

It depends on your architecture requirement.

answered Jan 23 '13 at 19:01

DcodeChef

1,550
13
17

Asynctask from non ui thread

3 Answers3

Linked