Using AsyncTask as Serializable or Parcelable --> To void activity destruction(orientation or during incoming phone call)

by Vikas » Tue, 04 Aug 2009 23:15:15 GMT

Sponsored Links
 Hi Guys,

I have a requirement where I have to read/parse some data from the
server(using HTTPConnection) and then display it on to the screen. To
avoid ANR issue I used AsyncTask to perform the above. Now in order to
avoid application crash in case the activity gets destroyed(either by
OS or if orientation changes or say on any incoming call-->where user
stays on the phone for long and for some reason OS destroys/recreates
the activity). Currently, I hols the reference of AsyncTask in my
activity and then provide a callback(the activity itself) to AsyncTask
so that I can pos back message to activity(like closing progress
dialog box).In order to avoid memory leaks on onPause I nullify this
activity reference in AsyncTask.Before onPause I save the AsyncTask
instance using onSaveInstanceState method but I have to use
putSerializable for that. I have read on the forums that serialization
method is slow, so my question is should I use parcelable approach(and
whether the converting AsyncTask to parcelable will be same as
creating any other object parcelable). or both these approaches are
totally wrong i.e. I should not be using both the above approaches if
no then what is the correct approach which gives maximum performance
benefits. No I read at one forum also on android blog(and in their
examples) where they suggest storing AsyncTask
using onRetainNonConfigurationInstance() method as that gives
performance benefits but I think that approach just works only for
cases where activity gets destroyed via orienattion changes but does
not cover other scenarios where activity gets destroyed because of
things like low memory, phone calls etc.

I would really appreciate if anybody has any suggestions or ideas on
how to do it right(or if somebody can confirm that whatever I am doing
is right and I just have to choose between parcelable or
serializable?). I am able to get it working very well, its just that I
am not sure if it can cause any issue in production.

This is such a common task and there is no good example for this and
looks like people are still scratching their heads on this.


Other Threads

1. My program if fine in emulator but not on device, Inflate Exception

I write a Gallery program to display photos from sdcard, it shows the
photos fine but when user clicks on photo, it needs to display a
dialogue box or toast, it also works in emulator but not in G1 device
it shows errors like
android.view.InflateException: Binary XML file line #46: Error
inflating class java.lang.reflect.Constructor
I could not find the right solution
Thank you


2. remove SMS notification

I have a BroadcastReceiver that fetches incoming SMSs. I need to know how
can I remove/cancel the notification for a particular SMS. I found no way to
list the contents of the notifications bar, and also only marking a SMS as
read doesn't do the trick.
Is it possible to remove a particular notification from the notification



3. How to Create a file in Android Emulator Phone Memory

4. nHD(360x640) Vs. hVGA(320x480)

5. How to invoke an inbuilt application like GPS or Camera by another application

6. Android repo is down ?

7. Listview display all available items with page scrolling instead of listview scrolling