Hi,

Thank you Dianne for your immediate response.
Finally, I found how to access a file located in the resources of an
other application (thanks to one of yours response) using the
following code.

Context currentCtx = ...;
Context otherCtx = currentCtx.createPackageContext(<package_name>,
Context.CONTENT_INCLUDE_CODE);
Resources otherRes = otherCtx.getResources();

I'm still not able to create an InputStream on the files located among
the source code of the other package, but this is finally no longer
relevant.

Thanks.

On 15 juil, 12:50, Dianne Hackborn <[email protected]> wrote:
> When two applications shared the same user ID, they well have the same
> identity.  They are indistinguishable as far as all permissions checks (both
> on the filesystem and through IPC calls) go.
>
>
>
> On Tue, Jul 14, 2009 at 12:02 PM, Aiili <[email protected]> wrote:
>
> > Hi,
>
> > I’m questioning about the shareUserId property and the best approach
> > to share files among applications (around 1Mo compressed).
>
> > More particularly, I’m interested to know what types of files are
> > covered with this flag, and which use cases are supported?
> > For example, does this flag allow an application M to access a file of
> > an application A:
>
> > -       located among its source code (i.e. that can be access from the
> > latter with getClass().getResourceAsStream(name) code) ?
> > -       located in its res/raw directory (i.e. that can be access from the
> > latter with the getResources().openRawResource(getResources
> > ().getIndentifier(name, type, package)).
> > -       located in its assets directory
> > -       located anywhere else (to be determined)
>
> > In fact, even if the activity M is started by the activity A, the use
> > of the extras of the Intent is not acceptable because of the size of
> > the files.
>
> > Finally, I read that another way to share files is to use a
> > specialization of the class android.content.ContentProvider. Using
> > this class with the appropriate permissions (Is it the shareUserId
> > property?), would allow the application A to copy all its resource
> > files into a directory (with the Uri: content://) and thus access them
> > from M. But this approach would result in duplicating those resources
> > files. So, is there a way to avoid this?
>
> > Thanks for your help.
>
> --
> Dianne Hackborn
> Android framework engineer
> [email protected]
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to