overlapping todos
This commit is contained in:
parent
7e1e2962d2
commit
11c2886578
2 changed files with 30 additions and 0 deletions
|
@ -0,0 +1,9 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2020-07-01T19:05:44Z"
|
||||
content="""
|
||||
This overlaps with [[publicurl_config_for_all_special_remotes]]
|
||||
but I think is a better approach, at least for most special remotes that is
|
||||
could support.
|
||||
"""]]
|
|
@ -0,0 +1,21 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 5"""
|
||||
date="2020-07-01T18:59:48Z"
|
||||
content="""
|
||||
[[generic_readonly_http_remote]] if implemented would accomplish the same
|
||||
thing as this todo.
|
||||
|
||||
The advantage to that idea is, it doesn't need modifications be made to every
|
||||
special remote that might end up exposed over http. As long as the special
|
||||
remote is not *too* special about how it mangles keys into paths, it
|
||||
can work for a lot of special remotes.
|
||||
|
||||
The directory special remote is a good example.. It would be weird for that to
|
||||
have http-specific configuration and complications.
|
||||
|
||||
And, that approach doesn't complicate the external special remote protocol,
|
||||
and avoids the problems discussed in comment #4.
|
||||
|
||||
So, I'm inclined to that approach over this one.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue