Hi Guich,

You're not alone in your misunderstanding of Android threading. However, if
you use AsyncTask correctly, you have a 99% chance of getting it right. Just
put any code that blocks, takes a long time, or can timeout into
the AsyncTask.doInBackground method instead of into an Activity method.

As an aside, the main UI thread is in way a lengthy task, but none of its
methods should be. This may be a generalization, but it should be idle most
of the time, ready to respond to user or lifecycle events.

On Wed, Feb 17, 2010 at 7:45 AM, guich <[email protected]> wrote:

> Hi,
>
> What's the main application thread used if not for lengthy tasks? I
> really can't understand all the threads of Android...
>
> regards
>
>   guich
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<android-developers%[email protected]>
> 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 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-developers?hl=en

Reply via email to