Hi Bob, thanks for the reply. What happens on the server is completely out of my hands. It is not part of my app, and it's not under my control. That said, the use of get to update the database is something that the server offers as a convenience. It's not the case the a user could inadvertently update data by retreiving a web page, for example. And as far as my app is concerned, the get is issued completely within my code; the user never visits the url within a browser. The user indicates within the app that data needs to be stored on the database, and the get is issued behind the scenes to store it.
I largely agree with your method for dealing with the destruction of the app after the issuing the update and before receiving the response. I think what I'm going to do is track the updates within a local database. When an update is issued, I'll create a record in the local database and set the status to pending. As each response is returned, I'll update the corresponding row in the database, setting the status to indicate success or failure. When the app returns after being destroyed, I'll access the local database and for each record which has a status of pending, I'll query the server to check whether the update succeeded. -- 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
