[android-developers] Re: android design considerations: AsynchTask vs Service (IntentService?)

On Oct 2, 10:13 pm, Dianne Hackborn <hack...@android.com> wrote:
>...
> And what you need to do with AsyncTask is *different* depending on where you
> are using it -- in an Activity, or a Service, or a View, or whatever.  They
> each have their own sometimes subtle details about lifecycle that you need
> to understand when introducing asynchronicity.  AsyncTask can't try to
> document exactly how to use it when combined with every other possible
> facility.

True, but that is exactly why the team writing the documentation
should have kept the following related question in the forefront as
they wrote it: given that such is the case, how -are- users supposed
to figure out the differences in different components? Trial and
error? Belated, confusing responses from Google Groups, forums and
email lists? Or by suitable cross-references from the Javadoc node on
AsyncTask?

You can guess which one of these options is my preference;)

--
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