Yes, I had watched that talk, and I agree that it was very interesting. The pattern of keeping track of requests in a local database might well be the way I end up going. It initially seemed as though that might be overkill for what I'm doing, but the more I think about it the more likely it seems that that is the right solution.
There is also a blog post by Romain Guy in which he recommends going through the code of Shelves to get some ideas about persistance when using AsyncTask. I did have a quick look at the code of Shelves a while ago, for something different, but I think it might be quite tricky sorting out the wood from the trees. -- 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
