On Tue, Nov 9, 2010 at 11:39 AM, kypriakos <[email protected]> wrote: >> (3) Use a ContentProvider >> (4) Use a remote Service >> >> I'd vote #3 or #4 for production. If you want to skate by with #2 for >> a prototype, that's reasonable. > > I agree with (3) as well for production - we may stick with (2) (/ > sdcard) only > for the time being during the prototype testing. Can you elaborate on > what > you mean by (4) - I think I understand but I want to see what you > wanted > to say there.
Use a Service that exposes some sort of API, typically through AIDL. >> Considering the extra complexity of maintaining two projects -- and >> the craptacular user experience from having these sorts of >> dependencies -- I am hoping that you have better reasons for keeping >> them separate than merely avoiding rework. > > Craptacular is the word here. Well, technically, I'm not sure it's a word, even though I used it... :-) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- 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

