Repository navigation
support sub-shares? #75
Description
What if you for instance get read access to /foo but write access to /foo/bar? In OCM that would be two separate shares, and if you open /foo and then drill down to /foo/bar, the receiving server will not recognise that you entered the folder where you do have read/write
Activity
smesterheide commentedon May 19, 2023
Seems right on the surface,
/foo/baris more specific than/foo. My question here is are we going to mimic POSIX file system permissions?glpatcern commentedon Sep 30, 2024
[Reviewing all outstanding issues] this is IMHO implementation-dependent, meaning that we may well have OCM implementations that use some POSIX-like ACLs and do the "right thing" (in the example, give write access to
/foo/bareven when browsing from a read-only/foofolder).As an example, this is how EOS works and how CERNBox exposes OCM shares.
The question is whether we want the spec to explicitly state what is the "right thing" to do, or whether to leave this aspect deliberately unspecified.