--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.
Hi.Content provider allows you to share databases between applications. If you do not have any additional requirements this is the best choice for you.
--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-platform/-/H0-pXOjmX88J.
kris
This is *not* a good solution. You should not be using the shared
user id, this will give you a lot more dangerous possibilities
Because what he's doing is exactly the use case for having a content
provider. This is just a quick fix to not have to write one. But in
general when you want to share data between apps, you write a content
provider. If the apps are tightly integrated enough that they need a
shared use ID, then why does he need two apps in the first place? I'm
not saying that sharedUserId is useless, I'm just saying that if you
want to do this, there's a tool that was created to handle it, why
throw that out the window.
kris