Ok, I think what we really need here is a concept of local application bundles in Oxide that doesn't involve using file URI's. Essentially, this would mean introducing a custom URI scheme (say, application://) where we give each application its own domain, and provide a way of mapping each domain to an application install on the filesystem. With this, code within an application would be able to access any file within its own bundle (because they have the same origin), but won't have access to other application bundles or other files on the filesystem.
Ok, I think what we really need here is a concept of local application bundles in Oxide that doesn't involve using file URI's. Essentially, this would mean introducing a custom URI scheme (say, application://) where we give each application its own domain, and provide a way of mapping each domain to an application install on the filesystem. With this, code within an application would be able to access any file within its own bundle (because they have the same origin), but won't have access to other application bundles or other files on the filesystem.
WDYT?