-
Notifications
You must be signed in to change notification settings - Fork 12
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
New storage layout extension NNNN-uri-direct-storage-layout #63
base: main
Are you sure you want to change the base?
Conversation
Should there be a note about the possibility of many to one mappings created by the idea of regex->string replacement? A warning or advice about what to do in the event of collision? Is the replacement strictly regex->string or is regex->regex-replacement intended? I ask because later there is a comment about static string replacement which sort of implies there might be something dynamic too How should multiple replacements be handled? Are the regexes applied in turn? Ie. does |
@alvinsw : Is this extension still of interest? There are open questions above. |
Yes I think the replacement is a weak point here. After discussion with @ptsefton we'll take off all the parameters including the one for string replacement. So the spec should be simpler and straightforward. |
We still need the layout option where we can directly map a URI to directory paths without any hashing. |
Thanks for replying @alvinsw . If you are still interested in moving this forward, could you push the update to reduce parameters you proposed in your Aug 9, 2023 #63 (comment). (We aren't sure whether #57 is going to move forward but anyway the comments from @neilsjefferies do not apply to your use case.) |
@zimeon I have updated the document and removed all parameters. Can this be approved now? |
We want to be able to directly map a URI into the storage layout directory.
It may be similar to #57 but simpler and just use the path of any valir URI directly.