So let me pitch the scenario first… My program requires the storage of files that should be accessible to all users. The idea is, I could upload a file then any other user would be able to read that file. It really is as simple as
name -> file. Ideally I would like a user to be able to see a list of all files that have been uploaded as a simple drop down menu. (This is an application where the scenario of uploading a file is very rare, but obviously needed.)
My question is; Is using the applications
own_container a sensible use case? My understanding is that the
own_container is like any other container (a
MD)… With the exception that it is always visible to the application (always has permissions) regardless of what user is using the application. The
own_container is the exact same
MD regardless of what user is using the application. Thus my idea is to use NFS emulation to simply store the files in this
MD, then any user that uses the application can read all the
File's that have been uploaded.
Is there a serious flaw in my understanding or am I understanding things correctly?
The one flaw I can think of is that it might be better to create a new MD, serialise it and store it in the apps
own_container. This would allow additional information to still be stored in the apps
own_container… Getting this idea from here: Accessing stored data without handle. I am guessing in that scenario it would have to be a public MD so that everyone would be able to write/read to it?
Any help or advice would be greatly appreciated.