Always demanding no waiting for async io to finish is not realistic since 
many applications cannot do useful work until the results are in over the 
wire. Results of network calls are often used as inputs to computations and 
not simply as populating views.  Until the computations are done, the app 
can really do no useful work.  In these cases, requiring no waiting on 
AsyncIO (.get() call) only vastly over-complicates the app for no 
beneficial purpose.

On Monday, August 17, 2009 at 10:49:29 AM UTC-4, Tom wrote:
>
> Hi, 
>
> I use a subclass of AsyncTask in the main Thread. 
> I would like the main Thread wait for the end of the AsyncTask. 
>
> How can I do that? 
>
> I saw methods "get()" in AsyncTask but I don't understand them. 
>
> Best Regards 
> Tom

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/c81c9884-80c0-4289-95e2-5f01f474e38c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to