0

I'm developing an app (Android 4.0) which relies on a background service to sync specific data from probably sqlite to a remote mysql database.

I am pretty new to Android dev (but not programming) and hence am still struggling with where to begin and how to construct the system. I am planning on leveraging:

"Developing Android REST client applications" by Virgil Dobjanschi (2010)

as a starting point. What he demonstrates is a high level approach to developing such a system which is excellent.

My question is, in two years or so has anything changed, or would this still be considered a viable approach? Any other help you can give having gleened my situation will help me immensely.

Thanks.

HGPB
  • 4,346
  • 8
  • 50
  • 86

1 Answers1

1

Here is an updated approach that I have found very useful

Use an Intent Service to get off the main thread for your requests. If you want more info about services refer to this.

Hope this helps!

Community
  • 1
  • 1
jjNford
  • 5,170
  • 7
  • 40
  • 64
  • Thanks! Instead of services could the system just be run off events. I noticed that services running all the time and can drain the battery? Using broadcasts/recievers could be an approach... – HGPB May 17 '12 at 14:25
  • A service is long running, and intent service is not. an intent service will execute the code then die. you could also just thread off the request. the intent service with a result receiver just makes a clean reusable way for a callback response to be triggered. – jjNford May 17 '12 at 15:11
  • Thanks again. Sounds like i could use an alarm broadcast to start my intent service, do some syncing and close it down (maybe). – HGPB May 17 '12 at 15:33
  • Yes you could do that for auto refreshes. The first restful request can also be triggered by an event either by the application or by android (like onResume() or some other listener) – jjNford May 17 '12 at 15:42