It isn't so much that I'm expecting the requests to be long-running, I'm not, but I do need to know that they succeed. I probably confused things by talking about *gets*. The application issues a get with parameters, and the server updates a database with the parameters, so although it's a get, it's not a read-only transaction, I need to be sure that my application can deal with the situation in which it issues a get and is then destroyed before it receives the response.
The reason for reusing the AndroidHttpClient is just to avoid the overhead of continually recreating it. The idea is to create it and then let it act as a conduit between the Android app and the server. -- 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
