Let me clarify: In this case I don't need or want to have the sync be very visible. I just want to enter some data on the device and sync it to the server eventually, so when the network connection is available. Batching would be OK too. Because that's kind of like editing a contact or updating a calendar I thought it would be suitable for a sync adapter, and I guess the sync framework also takes care of some things that I otherwise have to manage myself.
Could you elaborate on your statement that a sync adapter would be the right choice when it's tied to UI redrawing? I'd guess that the opposite would be true? Hugo On Jun 23, 11:34 am, Gyan <[email protected]> wrote: > Nice thought. But do you really think you need an adapter to answer this. > This is just a data sync functionality! If its tightly tied to UI > re-drawing/customization then you might go with writing SyncAdapter > otherwise you can, very well, stick with an interface! > > Thanks > Gyan -- 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
