Thanks Mark, > (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. > No. They won't be the same process, regardless. They run as the same > Linux user, which is what enables the file access. Gotcha. > Besides, what does it mean to "launch both apks"? APKs are not > launched, components are. Bad wording there - yes I meant the corresponding components. > 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. I will push for merging the work afterall as I can see the consequences of "masking" what would eventually be a bad user experience. I think it does make sense to get the code that was put in the main() classes of these projects (which was ridiculously bad coding) and move them into classes allowing the threading to work in a single process. I think after the prototype proves the concept I will rework. Thanks again for clarifying all this > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android Training in Atlanta:http://bignerdranch.com/classes/android -- 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

