Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss home logic #601

Open
labkode opened this issue Mar 26, 2020 · 1 comment
Open

Discuss home logic #601

labkode opened this issue Mar 26, 2020 · 1 comment

Comments

@labkode
Copy link
Member

labkode commented Mar 26, 2020

To simplify our lives:

  1. We need to include Separation of concerns: storage providers should not know about their mount path #578, that will mean that the SP responsibility is to always handle paths that start with root (/), only for forever, mount paths are left to the gw+registry.

  2. Assuming 1, we can configure a SP to be provider of a home. That means that this SP will need to map root(/) to a user home directory. Internal business is not exposed.

Having 1 and 2, we can enforce namespace in the gateway the following convention:

  • /home to always map to the home SP (this means GetHome() on the GW always returns /home)

Still leaving the possibility to expose the home SP under other paths:

  • /users/ can also be mapped to the home SP (this means GetHome() on the GW needs to take into consideration the user in context and reply with /users/hugo and use it for wrap/unwrap paths instead of just home. This model is particularly useful when exposing the home directory of a user in a global view.

With these changes there is not need anymore of having the GetHome method implemented in the SP and in the storage drivers, simplifying its implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants