whitemice wrote: > My application sits in its own namespace. I am only having conflicts > with different copies of the same Content Provider Component being > installed with different applications.
Don't use a ContentProvider. > This isn’t an issue, as my component is delivered as a small Java > class included with the main application. When activated, the > component inflates in size as it downloads content over the internet. > My goal is to manage this process by having only one component > activated regardless of how many applications are installed on the > device. Since the content in question is going on /sdcard (right? right?!?), solve the problem by managing the space, not managing the components. Since you already require each application to have your own code anyway, just use a regular Java class to access the /sdcard data store and dump the ContentProvider interface. > I agree that this needs to be improved, as there is currently no > support for components (downloading, versioning, upgrading, etc) in > Android or on the Android Market. I'm in total agreement on that point! -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
