02-06-2013 04:41 AM
Basically i want to open a file, view it, (maybe modify it and sent it back to my app).
Its important, that the file is not saved in the target-app (the data should only be viewed, not be duplicated).
if i use the invocation framework, i have the option to transfer the file by link.
The file then is stored in the target-apps "private inbox".
What exactly does that mean?
E.d. if i invoke the PDV-Viewer and sent the file to it, how is the file stored stored there?
When does ist get deleted?
Is it available in the viewer, after i close it? Can it be viewed again?
If yes, do i have any controll about it, e.d. delete it, after its viewed?
If i understood right, i can open a card withbb.action.VIEW. The card will appear, as a part of my app, but it will run in its own security context.
That means, i have no controll about the data, once its sent to the card?!?!
If i open a card, where will the data be stored and when will it be deleted?
Is it possible to create an instance of the PDF-Viewer inside of my app like the MediaPlayer or the WebView? (i dont think so )
Any ideas are welcome.
Sorry for the confusing post and my bad english.
02-06-2013 03:39 PM
Once you transfer the file, you dont have control over it. The target app will have access to it (R, W or RW). You can send it as read only though.
What I did not understand in your question is, why is deletion of the file important here? Once you gave the app read access, it can easily copy the content.
May be I am missing the use case here but please share more details.
02-07-2013 02:29 AM
Thx for the quick answer!
The problem is, that we want to store the files in a secure way and view it.
After a file is viewed, it will be stored secure again, so only our app has access to it.
Once its closed, there shall be no hint of that file at all in the target/viewing-application.
Even read-only is a big problem.
If an unencrypted copy of the file remains in the viewer-app, the encryption is pointless.
So i need to keep the data inside my sandbox, in memory or have controll about the handling of the file in the target app.
What i need would be: Store the file in my app, view it somehow, store it again. Without having other copies left.
I'm sorry, i can't give more detailed information.
02-11-2013 03:45 AM
02-11-2013 10:56 AM
In that case, Your requirement asks for writing your own viewer. If you want to have another app open this for you, you will have to share the data and the target app has to have access to the data to view it. However, the data will not be in a public space and only the target app will have access to it.
Hope this answers the question.