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
Approach 1:
User A shares the route by creating a file in the /inbox folder of User's B pod. This file contains the URI of the route shared.
Drawbacks
The routes of userA have to be inside a folder where everyone has access, such as /public. Security problems might arise as you can create infinite files inside your friends inbox.
Approach 2:
User A shares the route of User's B pod. Then, you do the following:
User A gives read permission to User B over the route shared.
User A creates a file in it's own POD inside /viade/routes/shared called userBwebID.json in where you store the URI of the route shared. In case this file already exist, a new entry is added for the shared route's URI.
User A gives User B read permissions over the json file.
Drawbacks
Im not sure by now on how to modify .acl files that give permission over folders and files, so further investigation is requiered.
The text was updated successfully, but these errors were encountered:
However, I believe following ViadeSpec will already decide for us this issue.
In order to read the routes, we all must write them in the same folder (either /viade or /public/viade), so depending on where the specification tells us to do so, we can already choose one approach or the other.
Not certain if I am correct, may easily be missing something.
Hi,
I'm taking a look to viadeSpec's issue concerning route sharing and I'm between two different aproaches:
User A wants to share a route to User B
Approach 1:
User A shares the route by creating a file in the /inbox folder of User's B pod. This file contains the URI of the route shared.
Drawbacks
The routes of userA have to be inside a folder where everyone has access, such as /public. Security problems might arise as you can create infinite files inside your friends inbox.
Approach 2:
User A shares the route of User's B pod. Then, you do the following:
Drawbacks
Im not sure by now on how to modify .acl files that give permission over folders and files, so further investigation is requiered.
The text was updated successfully, but these errors were encountered: