You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest a new service providing mountpoint-based binding to other services.
Each mount is a triple of (path, service operator, prefix), declaring that access to files under path should be forwarded to service operator, with path in their paths replaced with prefix. File access should always match the mount with longest common ancestor.
For example,
/, A, /
/dir, B, /test
Accessing /dir/a should be the same as accessing /test/a with B, accessing /b should be the same as accessing /b with service A.
Problem and Solution
This is because sometimes we may want to storage our data in different services, based on directories.
Additional Context
No response
Are you willing to contribute to the development of this feature?
Yes, I am willing to contribute to the development of this feature.
The text was updated successfully, but these errors were encountered:
Feature Description
I suggest a new service providing mountpoint-based binding to other services.
Each mount is a triple of
(path, service operator, prefix)
, declaring that access to files underpath
should be forwarded toservice operator
, withpath
in their paths replaced withprefix
. File access should always match the mount with longest common ancestor.For example,
Accessing
/dir/a
should be the same as accessing/test/a
with B, accessing/b
should be the same as accessing/b
with service A.Problem and Solution
This is because sometimes we may want to storage our data in different services, based on directories.
Additional Context
No response
Are you willing to contribute to the development of this feature?
The text was updated successfully, but these errors were encountered: