Hi All, Have a separate Async task class which serves the HTTP Request to all of your Activities and let your Activities implments a listener which helps the AsycnTask class to get the data from "onpostexecutes" method.
here is an example which i have written in a blog. http://www.androidsnippets.com/asyntask-in-android Mukesh On Wed, Nov 14, 2012 at 3:41 PM, TreKing <treking...@gmail.com> wrote: > On Tue, Nov 13, 2012 at 3:44 AM, Albertus Kruger < > albertus.kru...@gmail.com> wrote: > >> I would like to know if it is better to have seperate AsyncTasks for >> every screen on your application or is it better to have one AsynTask class >> that handles all processing from different screens on my application ? > > > One class that handles everything seems like a terrible idea. An AsyncTask > should represent a single task. It does one thing, reports progress on it, > and returns a result. That's it. > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > -- > 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+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Warm Regards, *Mukesh Kumar*, Android Consultant/Freelancer, India,Hyderabad. -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en