You might gain some good ideas from watching the RESTful application development video from this year's GoogleIO conference:
http://www.google.com/events/io/2010/sessions/developing-RESTful-android-apps.html I found it fascinating. On Dec 15, 4:28 am, flipside <[email protected]> wrote: > I'm developing an application in which the user will be firing off > http gets sporadically. Perhaps a burst of four or five, then a pause > for maybe a few seconds or or tens of seconds or a few minutes, and > then another burst. I'm familiar with HTTPClient in non-Android apps, > and it seems appropriate to use AndroidHTTPClient in this scenario. > I'm trying to determine the most efficient way to put it into a thread > and use it. > > The transient thread-creation methods such as AsynchTask and > IntentService don't seem appropriate, because the AndroidHTTPClient > will be lost when the task completes. Perhaps I should put into a > Service. I guess that what I'm trying to do is a pretty common > requirement and I was wondering if anyone had any pointers. I'm > thinking particularly about how best to cater for life-cycle events > and configuration changes that might affect ongoing requests. I'm > expecting most of the requests to be short-lived, but of course there > is no guarantee. -- 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
