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
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.
The text was updated successfully, but these errors were encountered:
To simplify our lives:
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.
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 justhome
. 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.
The text was updated successfully, but these errors were encountered: